Book Image

Infrastructure as Code with Azure Bicep

By : Yaser Adel Mehraban
1 (1)
Book Image

Infrastructure as Code with Azure Bicep

1 (1)
By: Yaser Adel Mehraban

Overview of this book

It’s no secret that developers don’t like using JSON files to declare their resources in Azure because of issues such as parameter duplication and not being able to use comments in templates. Azure Bicep helps resolve these issues, and this book will guide you, as a developer or DevOps engineer, to get the most out of the Bicep language. The book takes you on a journey from understanding Azure Resource Manager (ARM) templates and what their drawbacks are to how you can use Bicep to overcome them. You will get familiar with tools such as Visual Studio Code, the Bicep extension, the Azure CLI, PowerShell, Azure DevOps, and GitHub for writing reusable, maintainable templates. After that, you’ll test the templates and deploy them to an Azure environment either from your own system or via a continuous integration and continuous delivery (CI/CD) pipeline. The book features a detailed overview of all the Bicep features, when to use what, and how to write great templates that fit well into your existing pipelines or in a new one. The chapters progress from easy to advanced topics and every effort has been put into making them easy to follow with examples, all of which are accessible via GitHub. By the end of this book, you’ll have developed a solid understanding of Azure Bicep and will be able to create, test, and deploy your resources locally or in your CI/CD pipelines.
Table of Contents (17 chapters)
1
Section 1: Getting Started with Azure Bicep
6
Section 2: Azure Bicep Core Concepts
11
Section 3: Deploying Azure Bicep Templates

ARM and Bicep syntax comparison

Bicep has some syntax in common with ARM templates, though some simplifications have been made, as shown in the following table:

Now, let's look at some points you need to keep in mind if you wish to have a better coding standard in your team and cleaner templates.

Best practices for Bicep syntax

There are points you need to be cautious of regarding the Bicep syntax. First things first, avoid using reference or referenceId unless it's necessary. Your dependencies will either be implicitly inferred when you use a property of a resource or you use the dependsOn attribute.

Next, choose a casing standard for your team and stick with it. Many folks like camel case, and that is what the Bicep team uses as well:

var myCamelCaseVariable = 'Hi there!'

And last but not least, if you intend to add a description to a parameter, make sure it outlines what this parameter is used for to prevent confusion...