ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terraform
Set up Terramate stacks, git-based change detection, and generated backend config so CI runs terraform plan only on the monorepo directories that actually changed.
Migrate Terraform resource addresses safely with the 1.1+ <code>moved</code> block. Learn how it works, see a step‑by‑step example, and avoid common pitfalls for a smooth refactor.
Architecture note on using an S3 backend with native lockfile for Terraform state, covering requirements, trust boundaries, operational checks, failure modes, and when to reconsider the design.
Terramate's hierarchical globals and code generation eliminate Terraform boilerplate duplication across monorepo stacks. Define backend, provider, and version config once at the root, override per environment or region, and generate consistent HCL files in every stack directory.
Use Terramate's Git-based change detection to plan and apply only the Terraform stacks affected by a change, with dependency-ordered execution, verification steps, and recovery guidance.
Make Terraform deploy graphs explicit with Terramate stacks, render shared backend and provider config via code generation, and run only changed stacks to cut CI time and blast radius.
Learn how to move Terraform state to a remote S3 backend, enable DynamoDB locking, and avoid conflicts when multiple teammates run apply simultaneously.
Terramate’s Module Graph automatically discovers Terraform module dependencies, orders them topologically, and prevents cycles. Learn how to generate, inspect, and enforce the graph in a real repo.
Learn how to implement Terraform remote state using S3 and DynamoDB to prevent state corruption and enable secure team collaboration through state locking and IAM boundaries.