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

Idempotency and its importance

Idempotency means no matter how many times you run your pipeline or what the current state of your cloud resources is, you always get the same result at the end of your deployments.

Idempotency

For example, if your template is deploying a storage account in the first run, and then an additional storage account if you run it again, it is not idempotent. It is very important to keep your deployment idempotent to prevent any change in behavior, which makes troubleshooting a nightmare.

Immutability

Immutability is also something that you need to consider. Not only it is important to make sure your templates provide the same result at each run, but the configuration of your resources must be maintained if no change has been recorded.

These issues usually happen when you are not as confident about your cloud deployment as you are about your code and as such, your applications might suffer from slow memory, run out of disk space, and more. To...