Leveraging Bicep to deploy Azure resources - Part 1
Commencing today, we initiate a series of articles delving into the deployment of Azure resources using Bicep. Throughout this exploration, we will elucidate how this emerging practice aligns with the broader paradigm of infrastructure as code.
Over the past decade, the observed trend of cloud adoption has prompted numerous organizations to transition a multitude of their applications onto the cloud, encouraging a more profound embrace of this paradigm and this migration necessitated the adoption of more stringent processes for developing and deploying applications.
This trend primarily impacted applications, prompting engineers to increasingly adopt CI/CD best practices facilitated by the integrated tools offered by cloud providers, such as Azure DevOps, for instance.
A burgeoning trend is currently unfolding wherein automation extends beyond applications to encompass infrastructure. Resources are no longer manually allocated; instead, they are automatically provisioned through configuration files. This paradigm is commonly known as "infrastructure as code".
Various tools have surfaced to cater to the infrastructure-as-code paradigm, with Terraform and Ansible being among the most prominent. Recently, Microsoft has introduced a newcomer called Bicep, and in this series of articles, we will explore its application in real-world scenarios.
- Leveraging Bicep to deploy Azure resources - Part 2
- Leveraging Bicep to deploy Azure resources - Part 3
- Leveraging Bicep to deploy Azure resources - Part 4
The subsequent textbooks prove useful for concluding this series, addressing infrastructure as code as a comprehensive subject matter.
Terraform: Up and Running: Writing Infrastructure as Code (Brikman)
Getting started with Bicep: Infrastructure as code on Azure (Berson)
Without further ado and as usual, let's begin with a few prerequisites to correctly understand the underlying concepts. Continue here.