This presentation explores a Terraform-based approach to Infrastructure as code. Infrastructure is becoming more and more important for us as developers to understand and develop; it’s no longer only in the hands of the operations team. Terraform is a great tool for infrastructure management.
In this post, l explain how we used Visual Studio Code’s Development Container feature as a stepping stone in our long-term effort to achieve Collaborative Infrastructure as Code. This one step in the process gave a versioned, repeatable working environment and allowed us time to determine the next steps in the effort to achieve IaC.
Infrastructure as Code (or IaC) is the process of using code and versioning in the same way you do your source code to manage your networks, VMS, and Azure resources. IaC generates the same environment every time it is applied, and it’s an important DevOps practice to use alongside continuous delivery.
The release pipeline executes this model to configure target environments. If you need to make any changes, you edit the source, not the target environment. This allows you to create reliable and stable environments on-demand that can be validated, tested, and repeated.
In this blog, we’ll look at how we can use Azure CLI and Azure DevOps Release Pipelines to make this happen. I’ll walk you through all the steps you need to take to get set up.