IaC Automated Assurance
summary
Concrete toolkit: uses PowerShell + Pester to run linter and unit-style checks, invokes PSRule for Azure against compiled Bicep/ARM, and runs Azure what-if deployments to compare PR versus main. CI/CD integrations emit JUnit XML and write a human diff into the pull request. Checks catch missing soft-delete and replication, unused parameters, and resource ordering. Demonstration scales from a 24,000-line ARM down to a 10,000-line Bicep repo and the pipeline works in GitHub Actions and ADO.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:25PS Rules for Azure and Bicep
- 10:26Custom rules and suppression
- 19:00Bicep CLI and PS Rules limits
- 21:28Testing Bicep structure
- 26:29What-if deployments
- 31:02CI/CD with GitHub Actions
- 34:43Q&A
related talks
01h 05mAn Infrastructure as Code Bake-off, comparing ARM, Terraform and Bicep
38mState of Infrastructure as Code (IaC)
46mAutomating Infrastructure as Code with Azure DevOps
01h 02mBicep: Deploy to Azure cloud without it being a pain in the Arm
54mMastering Azure Well-Architected: From Pipelines to Perfection
57mModern Continuous Integration with Azure Pipelines
46mLeverage from Pester to automate Azure Storage Account testing
01h 04mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi