Terraform Practices - The Good, the Bad, and the Ugly
summary
Concrete checklist for Terraform: always lock versions for Terraform, providers and modules and avoid locking only minor ranges; enforce use default tags so every resource carries managed and billing tags; put state remotely and enable locking with remote state with DynamoDB lock to prevent concurrent apply conflicts; structure repo by team/project/cloud/region to keep state files small; run CI checks and automated applies with Atlantis + CI plan checks or remote execution to enforce formatting, docs and security policies.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:27Terraform implementations can be...
- 2:46Versions lock
- 3:17Tagging resources
- 5:03Remote state
- 5:59Community modules VS. Custom modules
- 8:24Modules side: Variables
- 8:44Modules side: Locals
- 10:07Variables & Locals
- 11:17Files Structure
- 12:51Applying classic code best practices
- 17:08Structuring your TF code base
- 21:02from TF docs #2 about Workspaces
- 23:17Terraform Execution
- 24:00Practices Enforcement
related talks
35mTerraform Practices - The Good, the Bad and the Ugly
41mTerraform Practices - The Good, the Bad, and the Ugly
30mTerraform Practices to Enable Infrastructure Scaling
15mTerraform Practices: The Good, the Bad, and the Ugly
39mTerraform Practices to Enable Infrastructure Scaling
31mTerraform Practices to Enable Infrastructure Scaling
01h 00mGotchas using Terraform in a secure delivery pipeline
24mTerraform Best Practices