Episode
Build a custom HTTP API using Azure Functions and Cosmos DB - Episode 4
Session four completes our series and we:
- Choose the optimal Azure service plan for our business requirements
- Configure GitHub actions as a CI/CD pipeline for the API project
- Configure CORS to enable a client app to communicate with the API
It's time to deploy our API to Azure. We choose a service plan that matches our business requirements use a CI/CD pipeline to transfer our project into the cloud. With GitHub Actions, we can focus on the app and trust that deployment will always work as expected.
We also get to meet a browser-based security feature called "same-origin-policy" that prevents our website from communicating with the API. To take care of this, we configure CORS (Cross-Origin-Resource-Sharing).
Session four completes our series and we:
- Choose the optimal Azure service plan for our business requirements
- Configure GitHub actions as a CI/CD pipeline for the API project
- Configure CORS to enable a client app to communicate with the API
It's time to deploy our API to Azure. We choose a service plan that matches our business requirements use a CI/CD pipeline to transfer our project into the cloud. With GitHub Actions, we can focus on the app and trust that deployment will always work as expected.
We also get to meet a browser-based security feature called "same-origin-policy" that prevents our website from communicating with the API. To take care of this, we configure CORS (Cross-Origin-Resource-Sharing).
Have feedback? Submit an issue here.