Re-potting Overgrown Terraform Repositories
summary
Demo splits a mono Terraform repo into two and then grafts them back using an AWS S3 backend with keys demo starting repo and demo web application, wrapper bash scripts, and Terraform state commands. The workflow copies state on init, uses Terraform state remove to strip modules (non‑destructively) from each state, and later uses Terraform state move to merge module.web_application back. End state matches deployed resources (plans show no changes). Sample repo: github.com/kristin-smith/terraform-demo.
AI-written summary · about
chapters (8)
- 0:00Introduction to repotting
- 1:07Why repot Terraform repositories
- 4:16Signs your repo is too big
- 8:30Signs your repo is too small
- 9:54Tools for splitting repositories
- 13:09Demo splitting the mono repo
- 17:40Demo rejoining split repos
- 22:46Key takeaways and conclusion
related talks
35mMisadventures with Terraform
59mManaging Terraform modules at scale
19mSynchronization of Infrastructure Provisioning & Application Deployments
15mTerraform, GitOps & Kubernetes: manage infrastructure & aas
01h 01mTaming Infrastructure Workflow at Scale
15mTerraform Practices: The Good, the Bad, and the Ugly
01h 32mUsing Terraform and AWS to create environments on the fly
06mIGNITE: Terraform Practice to Enable Infrastructure Scaling