Terraform: A Novel About Modules, Providers, Security, and Pain
summary
Practical use of Terraform on Azure and AKS with a concrete module/provider strategy that includes a custom Go provider and a small Go credential wrapper. Covers per-environment state management with separate backup state and key rotation, Vault for dynamic credentials, Terragrunt for backend templating, and a CI that runs hundreds of Terraform jobs weekly; new modules take ~2 weeks to harden and test clusters cost ~$300–350/month. Discusses operational pitfalls and recovery workflows (count/depends_on, imports, backend interpolation).
AI-written summary · about
chapters (6)
- 0:00Introduction
- 10:40Terraform pain points
- 17:04Security and state
- 23:26Infrastructure automation
- 28:04Security testing
- 33:45Conclusion & Q&A
related talks
43mDemystifying Terraform - "Hardcore" to Core Infrastructure... Tool
46mTerraform best practices with examples and arguments
46mTerraform best practices with examples and arguments
31mTerraform Practices to Enable Infrastructure Scaling
41mTerraform Practices - The Good, the Bad, and the Ugly
35mTerraform Practices - The Good, the Bad and the Ugly
31mTerraform Structure & Enablement
30mTerraform Practices to Enable Infrastructure Scaling