ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terraform
How Terramate’s stack‑based change detection works, what it requires, where trust boundaries lie, and how to verify selective execution in practice.
Stop duplicating Terraform directories for every environment. Learn how Terramate's orchestration layer uses stack templates to maintain DRY infrastructure across multi-account deployments.
Prevent state corruption in AWS by implementing Terraform state locking with DynamoDB. Learn the minimal design, IAM requirements, and how to handle stale locks.
Terramate’s policy feature lets teams codify governance rules that run before every Terraform plan. Learn how to write a simple policy, run it in CI, and weigh the trade‑offs of adding policy evaluation to your workflow.
Learn how to run Terraform commands only on the stacks whose files have changed since the last Git commit using Terramate’s --changed flag.
Learn how to use Terraform's for_each meta-argument to dynamically create multiple AWS security groups from a single resource block, reducing duplication and improving maintainability.
Learn how Terraform’s for_each meta‑argument lets you create multiple, uniquely identified resources with fine‑grained state control. This guide covers syntax, benefits, trade‑offs, and a step‑by‑step verification workflow using AWS security groups.
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.
terramate
dynamodb
aws
git