Getting started with Azure Bicep
At the time of writing, Azure Bicep is still in early development and not production ready yet, but this could change by the time you read this.
The main purpose of Azure Bicep is to do the following:
- Alleviate the complexity of the ARM template language to make it less verbose and to bring a more developer-friendly approach.
- Compiling Bicep files to produce a single ARM template. This prevents the use of a storage account or any other publicly available location for storing linked templates.
Unlike Terraform, Bicep remains Azure-specific. You can think of it as the next generation of the ARM language. To know more about Bicep and to stay tuned, you should subscribe to the Azure Bicep repo at https://github.com/Azure/bicep. Now we will redeploy exactly what we deployed previously, but we'll use raw ARM templates and evaluate the benefits of using Bicep. In order to perform this exercise, you must go through the following steps...
