Publish reusable Bicep code by using GitHub Actions
Publish Azure template specs and Bicep modules by using a deployment workflow. Automatically validate and add versioning to your reusable Bicep code.
Learning objectives
After completing this module, you'll be able to:
- Publish Bicep modules to a private registry from a GitHub Actions workflow
- Publish Bicep files to a template spec from a GitHub Actions workflow
- Automatically add version numbers to your modules and template specs
Prerequisites
You should be familiar with using:
- Bicep modules and module registries.
- Azure template specs.
- The Bicep linter, along with testing your Bicep code.
- Azure, including the Azure portal, subscriptions, resource groups, and resources.
- Basic Git commands, including cloning, committing files, and pushing changes to GitHub.
- GitHub Actions, including jobs, steps, and secrets.
To work through the exercises in the module, you'll need:
- An Azure account that has the ability to assign roles and to create resource groups and Microsoft Entra applications.
- A GitHub account.
You'll also need the following items installed locally:
- Visual Studio Code
- The Azure Account extension for Visual Studio Code
- The Bicep extension for Visual Studio Code
- The jq command-line JSON processor
- The latest Azure CLI tools or the latest Azure PowerShell version
- Git