The board of the shelter is rather pleased. You've updated the application with a new feature, configured security checks, and created an environment in Azure to host the project. The time has come to deploy the project!
Because the application will continue to grow with new features in the near future, the board wants to ensure the deployment process is streamlined. Whenever new code is pushed to main it should be deployed to production.
You will complete this hack by creating one last GitHub Action to deploy the project to Azure. Deploying a project can be rather complex depending on the services being used and service level agreement (SLA) which needs to be met. For example, you may need to configure blue/green deployment to ensure no downtime when new features are published. You can talk about different scenarios with your coach.
For purposes of this hack, you will deploy to the environment you created earlier when code is pushed into main.
- Demonstrate a GitHub Action is created which deploys the website to Azure Container Apps when code is pushed into
main - Verify the PR you created earlier is pushed to
main - Demonstrate that the public site displays the shelter's application, including the hours information from the component you created earlier
- Understanding GitHub Actions
- Triggering a workflow
- Publish revisions with GitHub Actions in Azure Container Apps
- Azure Container Apps Build and Deploy - GitHub Actions
- GitHub Actions contexts
- GitHub Actions encrypted secrets
- You can concatenate strings when defining a workflow using secrets or variables and string literals
- The name of the Azure Container Registry will be
<your_prefix>acr - The name of the Azure Container App will be
<your_prefix>containerapp - The name of the Azure Container App Environment will be
<your_prefix>containerappenvironment