IaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
summary
Live demo builds a .NET Razor dad app in App Service and exports the ARM JSON, shows Bicep decompiles that ARM into a much terser, Azure-native DSL (Bicep decompiles ARM), then compares Terraform (cross‑cloud, provider model, local TFstate that often contains plain‑text secrets) and Pulumi (use C#/TS/Python to program infra). Terraform workflow is plan/apply/state and requires remote locking to be safe; the demo deploys successfully but flags that state file contains secrets and needs secure remote storage.
AI-written summary · about
chapters (9)
- 0:00Welcome and introduction to infrastructure as code
- 1:08Why IaC matters
- 4:23ARM templates explained
- 18:44ARM in Visual Studio
- 28:44ARM with VS Code
- 38:19Bicep vs ARM
- 46:11Terraform for cross-cloud infrastructure automation
- 55:45Pulumi in any language
- 1:03:01ARM Bicep Terraform Pulumi
related talks
01h 00mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
01h 05mAn Infrastructure as Code Bake-off, comparing ARM, Terraform and Bicep
53mInfrastructure as Code on Azure: Bicep vs Terraform vs Pulumi
27mEvaluating Your Toolbox
49mTo Bicep or to Terraform - That is the Question
48mState of Infra-as-Code
58mDeploying Cloud Infrastructure using Pulumi
01h 02mBicep: Deploy to Azure cloud without it being a pain in the Arm