Terraform Practices: The Good, the Bad, and the Ugly
summary
Advocates a concrete repo layout—team/project/cloud/region—that keeps each state small to limit blast radius and enables Terraform-as-a-platform; uses remote execution, plan files and reasonable timeouts to avoid stuck applies; recommends wrapping Terraform workspaces with wrapper to prevent accidental selects and notes visibility pitfalls; enforces quality with tests, pre-commit, and Atlantis + GitHub Actions so PRs run plans and only merge when checks (formatting, docs, required tags for cost) pass, which keeps main in sync and reduces drift.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:09File structure standards
- 2:02Best practices for code
- 4:26Planning for the long haul
- 6:07Workspaces and their utility
- 8:26Terraform execution strategies
- 10:31Enforcing practices
- 12:29Envisioning infrastructure
- 14:43Closing remarks
related talks
41mTerraform Practices - The Good, the Bad, and the Ugly
35mTerraform Practices - The Good, the Bad and the Ugly
29mTerraform Practices - The Good, the Bad, and the Ugly
31mTerraform Practices to Enable Infrastructure Scaling
30mTerraform Practices to Enable Infrastructure Scaling
06mIGNITE: Terraform Practice to Enable Infrastructure Scaling
35mMisadventures with Terraform
46mTerraform best practices with examples and arguments