TECH BASICS

Introduction to Azure Bicep: Part 2

Azure | Cloud | IaC | DevOps | Automation

Photo by Fidelia Zheng on Unsplash

Before we move on, here is the link for part-1 — https://arunksingh16.medium.com/introduction-to-azure-bicep-part-1-902ccf2b260e

In previous post we talked about very basic stuff in respect to bicep. In this post I will try to cover few more concepts which is required to understand Bicep. If you are coming from Terraform background then the questions you may think of state, modules, templates extra. Let’s find out answers for those.

Bicep and Immutability

With Bicep, when a new deployment is executed, it creates a new set of resources based on the desired state defined in the code. If there are any changes to the code or desired state, a new deployment is executed to create a new set of resources. The previous resources are not modified, but they are replaced with new ones. This approach has several advantages, such as ensuring consistency, reliability, and predictability of the infrastructure.

How Bicep maintains the state?

Bicep does not maintain the state of resources on its own. Instead, it is used to create, update, or delete Azure resources using Azure Resource Manager (ARM) templates. The state of the…