An Infrastructure as Code Bake-off, comparing ARM, Terraform and Bicep - Mike Benkovich

Infrastructure as Code comes in many flavors, and the Azure Cloud's default deployment templates work with Azure Resource Manager (ARM) to define and deploy infrastructure. Working with the JSON format of ARM can be challenging, but Microsoft has introduced a language processor called Bicep which generates ARM as output. At the same time there are other options, including scripting tools, Terraform, Pulumi, Ansible and others. In this session we'll compare creating infrastructure using ARM, Terraform and Bicep, and compare pros and cons to each.
Check out our new channel:
NDC Clips:
‪@ndcclips‬
Check out more of our featured speakers and talks at
ndcconferences.com/
ndclondon.com/

[@alioughana]

Just a slight correction - ARM/bicep doesn't at the moment allow for keeping track of what's been deployed to Azure. You can certainly see the deployment logs for a deployment in Azure but there is no equivalent of Terraform state or Cloudformation stacks. However, there is a new type soon to be made available called 'deploymentStacks' that will enable you to manage the lifecycle of your deployed resources

[@illiakailli]

Thanks for the presentation!
Is there a way to generate an execution plan with arm/bicep before applying infrastructure changes? Both terraform and pulumi support this feature.