ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terramate
Terramate’s dependency graph automatically orders Terraform modules, ensuring deterministic applies. This guide shows how to declare dependencies, inspect the graph, and avoid common mistakes.
Learn how Terramate identifies changed Terraform stacks via git diff and runs applies only where needed, with a concrete example and verification steps.
When 'terramate run --changed' skips stacks that should have changed (or flags ones that shouldn't), the cause is usually git state — shallow clones, wrong base branches, or undeclared module relationships. A diagnostic guide with ordered checks and fixes.
Stop copying and pasting HCL across environments. Learn how Terramate's Stack abstractions separate infrastructure intent from implementation to scale Terraform deployments.
Orchestrating Multi-Stack Dependencies Terramate functions as an orchestration layer that generates Terraform-compatible files from templates defined in terramate.tm.hcl . When managing a complex infrastructure hierarchy, a common requirement is the propagation of output values from a base networking stack to multiple downstream application stacks. Integrati
The goal is to determine whether Terramate provides a clear indication when a stack run ends because a user pressed Ctrl+C versus when it stops due to the --timeout limit being exceeded. Currently, Terramate forwards interrupt signals to the underlying Terraform process and aborts on timeout, but both scenarios result in a non‑zero exit code and similar log
Goal Turn Terramate’s experimental drift detection output into actionable notifications that highlight meaningful infrastructure drift while keeping alert volume low in a multi‑stack Terraform environment. Constraints Terramate’s drift detect command is experimental and returns a flat list of drifted resources without a severity taxonomy, and it provides no
When executing Terramate orchestration commands against multiple Terraform stacks in parallel, the observed latency grows disproportionately compared to running the same stacks sequentially. The goal is to determine whether this latency originates from Terramate’s internal templating or dependency‑resolution layers, the Go runtime’s concurrency handling, or
Goal Determine whether Terramate’s point‑in‑time restore automatically validates data integrity and how it resolves conflicts with an existing live dataset. Constraints The documentation does not specify if checksums are recomputed during verification. Version differences may affect interpretation of backup files, causing inconsistent verification outcomes.
git