Azure, Infrastructure as Code, Bicep and DevOps - llewellyn-marriott/notes GitHub Wiki

Some WIP notes/rant about IaC on Azure

When an engineer first encounters the current IaC solution, they tend to be overwhelmed (rightfully so) by the complexity. They think to themselves "Why is this so complicated? we just need a single, simple repository with a pipeline and a folder structure that allows people to put in some bicep code and run a deployment"

But they only see the tip of the iceberg, what lies below is painful to account for:

• Dealing with deployment parameters
• Bicep modules and versions
• Making sure you can test it locally
• Slow pipelines
• PowerShell scripts all over the place
• Shared resources
• What-if results
• Deployment errors
• Clean-up/decommissioning of old deployments