An Infrastructure as Code Bake-off, comparing ARM, Terraform and Bicep
summary
Live demo builds a small .NET web dad app and deploys it to Azure via three IaC paths: raw ARM JSON (edited in VS/VS Code), Bicep (decompile ARM → decompile arm to bicep then compile to ARM) and Terraform (init, plan, apply). Shows VS/Code tooling, Key Vault for secrets, GitHub Copilot help, and module/parameter patterns. Notes: Bicep is cleaner for Azure-only work; Terraform handles multicloud but requires explicit state management and warns that terraform state contains secrets unless secured.
AI-written summary · about
chapters (7)
- 0:00Introduction to Infrastructure as Code tools
- 12:30ARM templates deep dive
- 29:46ARM with VS Code & Copilot
- 39:55Bicep vs ARM
- 49:21Terraform multi-cloud
- 57:53Pulumi & Ansible overview
- 1:02:27Choosing IaC tool & Q&A
related talks
01h 04mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
01h 00mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
53mInfrastructure as Code on Azure: Bicep vs Terraform vs Pulumi
01h 02mBicep: Deploy to Azure cloud without it being a pain in the Arm
27mEvaluating Your Toolbox
48mState of Infra-as-Code
49mTo Bicep or to Terraform - That is the Question
38mState of Infrastructure as Code (IaC)