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

Summary

In this chapter, you learned how to create a GitHub Action workflow from a YAML file in your source code repository. You learned how to create a service principal and create secrets in your repository to be accessed within your GitHub Action.

Then you saw how to add the necessary steps to validate and deploy your templates using two different actions, the Azure CLI and Azure ARM. We finished the chapter with two different ways to access the output of our deployment templates, both via environment variables and outputs of the previous step.

You now should be very proud to have come so far, but we have just a few more points to review before jumping into our editors and starting to write our templates. In our last chapter, we will review some best practices that will help you to really stand out from the crowd when it comes to infrastructure as code. So continue to find out more – you are nearly there.