Part 2: What is Bicep, anyway?
The inexperienced developer opens up the Azure portal and starts clicking away, randomly setting flags and switches until they get something to work as they expect. Don’t be that guy.
Part 3: Creating Bicep Files
There are several ways that you can create Bicep files and importing an existing Azure resource into VS Code is one of the easiest ways to do it!
Part 4: Naming things is hard!
Creating Bicep files is easy but creating GOOD Bicep files gets rather difficult!
Part 5: Using a Bicep Container Registry
Referencing a Bicep module in a registry is almost exactly the same as referencing a Bicep file in your repository.
Part 6: Azure DevOps Pipeline Layers
As it is with naming, creating good reusable pipelines and templates is very hard to get right. I look at it in a layered approach, much like a chocolate cake…
Part 7: What is “azd” and why should I care?
The Azure Developer CLI (azd) is an open-source tool that accelerates the time it takes for others to start using your project.
Part 8: PSRule Validation
PSRule is a great addition to a project and can be very useful to help make sure your Bicep modules are safe and secure.
Part 9: Adding an Azure DevOps Security Scan
The Microsoft Security DevOps for Azure DevOps module is available now as a marketplace add-on for Azure DevOps
Part 10: Convert Azure DevOps Pipelines to a GitHub Actions
GitHub Actions Pipeline Importer is coming to you soon!