Terraform Best Practices
summary
Practical checklist for using Terraform with GitOps: Terraform's declarative state and large ecosystem (≈3,500 providers, ≈15,000 community modules) enable versioned rollbacks and consistent environments. Use infraCost, terrascan, tfsec and tribi for cost and security scanning; address drift (resources changed outside code) as the main failure mode. Dragon Drop presents the open-source tool Cloud con Search to detect unmanaged resources, generate import blocks and state files, integrate infraCost/terrascan/tfsec/tribi, and open pull requests containing the reports.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:48Cloud maturity
- 2:51Infrastructure as code
- 8:19Why use Terraform
- 10:51GitOps
- 11:37Terraform and GitOps
- 13:24Terraform declarative nature
- 15:55Common Terraform obstacles
- 17:42Drift handling strategies
- 20:34Cloud Con Search tool
- 22:41Conclusion
related talks
29mTerraform Practices - The Good, the Bad, and the Ugly
30mTerraform Practices to Enable Infrastructure Scaling
35mTerraform Practices - The Good, the Bad and the Ugly
32mManaging Terraform resource drift using the GitOps method
41mTerraform Practices - The Good, the Bad, and the Ugly
31mTerraform Practices to Enable Infrastructure Scaling
46mTerraform best practices with examples and arguments
01h 00mGotchas using Terraform in a secure delivery pipeline
