IaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
summary
Demonstrates building an Azure web app stack (resource group, App Service plan, Linux site, app settings) four times using ARM JSON, Bicep, Terraform and Pulumi, and shows each deploy actually succeeds. Key points: ARM/Bicep run against Azure’s native store with no separate state file; Bicep decompiles ARM to readable code and transpiles back to ARM; Terraform uses a local/remote state and the terraform plan/apply workflow; Pulumi uses real languages and the Pulumi cloud stack to perform deployments.
AI-written summary · about
chapters (8)
- 0:00Welcome
- 1:34Introduction
- 6:54IaC tools overview
- 10:47ARM templates deep dive
- 22:39Bicep introduction
- 38:24Terraform multi-cloud
- 55:02Pulumi developer IaC
- 1:02:27Tool comparison
related talks
49mTo Bicep or to Terraform - That is the Question
41mInfra as Code with Pulumi
59mBicep - Deploy to Azure cloud without it being a pain in the ARM
53mInfrastructure as code - is it really?
24mWell-Architected Framework: Operational Excellence
51mInfrastructure as Real Code - An Intro to Pulumi
19mOptimize Azure Infrastructure as Code Deployments with VS Code
44mPulumi: Love And Azure