ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terramate
Running every Terraform root module on every commit wastes CI and hides risk. Terramate stacks plus change detection let you plan only affected code—if your Git metadata is sound.
Learn how Terramate’s change‑detection driven <code>--only-changed</code> flag lets CI run Terraform only on affected stacks, cutting plan/apply time in large monorepos.
Learn how Terramate builds and validates a deterministic dependency graph, the minimal design to implement it, and the operational checks that keep your IaC pipeline safe from cycles, missing edges, and version drift.
Terramate's change detection and explicit stack ordering let CI run only the Terraform stacks affected by a change, in the right order. Here's how after/before/wants work, with a worked example and the caveats.
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.
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.
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.
terraform