Terraform in Depth QA and Fireside Chat
summary
Explains concrete fixes: use depends_on to force deletion order, use data sources to import existing domains and networks, and prefer OIDC over storing AWS creds; recommends S3+Dynamo state with isolated buckets, backups and restricted CI-only access with an audited escape hatch. Advises smaller projects and frequent applies to speed plans, avoid circular graph edges by passing URLs or rearchitecting, use Terragrunt for per-environment deployments, and notes Open Tofu mostly stays compatible with Terraform.
AI-written summary · about
chapters (18)
- 0:00Introduction and Q&A setup
- 0:28Resource deletion order with depends_on
- 1:53OpenTofu and Terraform parity importance
- 2:56Handling pre-existing infrastructure
- 4:00Efficiency and speed in Terraform
- 5:23Recursive relationships in Terraform
- 7:50Custom plan/apply actions in pipelines
- 8:53Terraform for legacy data centers
- 10:16GitLab/GitHub pipeline customization
- 13:06Backend state management best practices
- 15:32Cloud account strategies for environments
- 17:58TFR files and team collaboration
- 18:41Book audience and content overview
- 20:03Workspaces and repository structure
- 21:50Decomposing Terraform projects
- 24:20Locking down state files access
- 26:05Managing Terraform code complexity
- 28:09Q&A wrap-up and closing
related talks
41mTerraform Practices - The Good, the Bad, and the Ugly
35mMisadventures with Terraform
35mTerraform Practices - The Good, the Bad and the Ugly
29mTerraform Practices - The Good, the Bad, and the Ugly
30mTerraform Practices to Enable Infrastructure Scaling
01h 00mGotchas using Terraform in a secure delivery pipeline
15mTerraform Practices: The Good, the Bad, and the Ugly
31mTerraform Practices to Enable Infrastructure Scaling