ARM deployments using Bicep, the Azure CLI, and GitHub Workflows

In this tutorial I explain how to run Bicep templates deployments from a local environment using the Azure CLI, and how to do the same using GitHub Workflows. The tutorial also explains how GitHub Reusable Workflows and naming conventions can be used to handle Bicep templates for multiple environments (e.g. DEV, TEST, PROD).

This is the fifth tutorial in a series made to speak about running Python web applications in Azure, using GitHub for the CI/CD part. The principles described here apply to other kinds of technology stacks, not only web applications implemented using Python.

Contents
(0:00:00) Intro
(0:00:45) Describing the Bicep template
(0:03:46) Using the Azure CLI
(0:10:30) Running the deployment locally
(0:15:13) Deployment completed
(0:16:27) Using GitHub Workflows
(0:17:15) Reusable Workflows
(0:22:06) Using psql to create a DB user
(0:23:30) Configuring secrets
(0:29:15) Running the workflow
(0:33:50) Application settings in Bicep
(0:36:44) Closing

The source code of the demo project is available here:
https://github.com/Neoteroi/Torino

For information on how to install the Azure CLI and support for Bicep templates:
* https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
* https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/install

The articles mentioned in the tutorial, regarding the complications of deploying Python web applications in a service like Azure Application Service, are these:
* https://azure.github.io/AppService/2020/12/11/cicd-for-python-apps.html
* https://www.nylas.com/blog/packaging-deploying-python/