Infrastructure Changes, So Modularize and Version Your...
summary
Argues that concrete module boundaries and strict versioning stop churn: use Terraform-style outputs so split modules by build, e.g. networking -> compute -> services, feed outputs between layers, and run phase deployments in CI. Put reusable pieces in a child modules repo, tag versions, and have pipelines bump references (example bump to v1.24 when promoting). Claims this pattern isolates new deployment contexts and lets fixes in dev be promoted reliably to production.
AI-written summary · about
related talks
31mTerraform Practices to Enable Infrastructure Scaling
41mScaling Infrastructure as Code
35mTerraform Practices - The Good, the Bad and the Ugly
30mTerraform Practices to Enable Infrastructure Scaling
06mIGNITE: Terraform Practice to Enable Infrastructure Scaling
48mCodifying Infrastructure with Terraform for the Future
59mManaging Terraform modules at scale
44mTaming the cloud sprawl