State of Infrastructure as Code (IaC)
summary
Shows concrete moves: a MCP server that feeds live docs and Azure verified modules to models, an interactive Bicep console REPL and reduced short‑circuiting to speed dev/test, portal “open in VS Code” that generates Terraform/Bicep and creates a repo, resiliency decorators like retry on and only if not exist, pre‑flight policy checks plus readable Bicep snapshot state validation, MS Graph and AZ API extensions for day‑zero surfaces, and what‑if noise reduction — all shipped or in preview with demos and experimental flags.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:53Why IaC matters
- 3:39AI-assisted IaC authoring
- 6:07Bicep dev test loop
- 10:42Terraform from Azure portal
- 17:42Resiliency for deployments
- 22:40PR review tools
- 29:43Deployment updates
- 33:39Troubleshooting stacks
- 35:23Summary
related talks
48mState of Infra-as-Code
01h 05mAn Infrastructure as Code Bake-off, comparing ARM, Terraform and Bicep
32mCode Quality and Infrastructure as Code
35mIaC Automated Assurance
34mIaC – Improving and Securing Infrastructure Provisioning in the Cloud
44mInfrastructure from Code: The Next Generation of Cloud Management
46mImplementing Infrastructure as Code
28mFrom Infrastructure as Code to Environment as Code: Challenges scaling IaC