IaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
summary
Compares Azure Resource Manager/ Bicep, Terraform and Pulumi by showing actual deployments: uses Azure CLI to provision resource groups and AKS, decompiles an exported ARM JSON into readable Bicep modules and deploys them (no external state), runs terraform init/plan/apply to create a web app (noting Terraform state file stores secrets in plain text so backends and locking matter), and demos Pulumi generating infra in C#/Go/JS via the Pulumi service; live demo authenticates with device code and the deployments complete.
AI-written summary · about
chapters (13)
- 0:00Introduction to IaC
- 7:07Why IaC matters
- 10:21ARM/Bicep vs Terraform vs Pulumi
- 17:03ARM templates deep dive
- 24:34Bicep for Azure
- 32:05Terraform fundamentals
- 41:22Terraform demo challenges
- 46:02Azure API vs AzureRM in Terraform
- 48:14Pulumi multi-language IaC
- 50:22Azure Verified Modules
- 51:03Tool comparison guide
- 57:32IaC adoption key points
- 58:35Final thoughts & Q&A
related talks
01h 04mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
53mInfrastructure as Code on Azure: Bicep vs Terraform vs Pulumi
27mEvaluating Your Toolbox
01h 05mAn Infrastructure as Code Bake-off, comparing ARM, Terraform and Bicep
58mDeploying Cloud Infrastructure using Pulumi
49mTo Bicep or to Terraform - That is the Question
53mInfrastructure as code - is it really?
48mState of Infra-as-Code