Top Ten Terraform Trip-Ups
summary
Top ten concrete pitfalls when deploying Azure data platforms with Terraform: using remote state to stitch parent/child configs exposes and reverts definitions; subscription-level role assignments often require Owner scope so restricting to resource-group creation reduces permissions; many role assignments need an Azure AD lookup (object IDs) or end up with hard-coded GUIDs; Terraform backend storage uses the account access key so use separate storage accounts per environment; Databricks and similar need multi-phase deploys because providers instantiate before resources exist; private endpoints break data-plane API calls; CI agents lock state and require a force-unlock pipeline policy.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:40Existing infrastructure irritation
- 3:45Pernicious permissions
- 6:14Azure AD agony
- 8:45State store snafu
- 10:51Environment testing pitfalls
- 13:40Provider problems
- 16:06Module malarkey
- 18:12Data plane disasters
- 19:54DevOps pipeline traps
- 20:37Closing remarks
related talks
01h 00mGotchas using Terraform in a secure delivery pipeline
29mTerraform Practices - The Good, the Bad, and the Ugly
50mTerraform 101: Building Repeatable, Secure Azure Infrastructure
35mMisadventures with Terraform
30mTerraform in Depth QA and Fireside Chat
35mTerraform Practices - The Good, the Bad and the Ugly
43mDemystifying Terraform - "Hardcore" to Core Infrastructure... Tool
41mTerraform Practices - The Good, the Bad, and the Ugly