ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terramate
Use Terramate stack dependencies and terramate run to execute Terraform commands across multiple stacks in the correct order.
Run terraform plan and apply only in stacks with modified files using terramate run --only-changed, reducing execution time and preventing unintended infrastructure changes.
Terramate adds a stack-and-blueprint orchestration layer above Terraform to eliminate copy-paste drift across accounts and regions. This post walks through a concrete VPC blueprint, generated HCL, and the run-time orchestration that keeps large fleets consistent.
Terramate streamlines Terraform by organizing code into stacks, generating reusable templates, and orchestrating incremental runs. This guide covers the minimal setup, trust boundaries, operational checks, failure modes, and when to evolve the architecture.
Guide to deciding when to use Terramate's code generation for DRY Terraform, with a comparison table, trade‑offs, and a step‑by‑step validation example.
Learn how Terramate’s changed‑only flag limits Terraform execution to stacks with actual file changes, speeding up CI pipelines and reducing risk.
Stop running 'terraform plan' on your entire monorepo. Learn how Terramate uses git-aware change detection to isolate infrastructure updates and reduce CI pipeline duration.
Use Terramate’s CLI run command to apply plan, apply, or destroy across multiple Terraform environments in a monorepo, with stack filtering, Terraform version alignment, and verification steps.
Use Terramate git-aware change detection to run Terraform only on stacks modified since a git reference, skipping unchanged infrastructure.
terraform
git