terragrunt-workflowslisted

# Terragrunt Workflows Terragrunt-specific orchestration. Pairs with the `terraform-workflows` skill — its cross-cutting rules apply on top of this skill's. See [Cross-skill notes](#cross-skill-notes) for the exact boundary. ## When to invoke **Symptoms:** - A command that worked last quarter now warns or fails: `--terragrunt-*` flag deprecated, `run-all` deprecated, "unknown command" for what used to be `terragrunt plan`. - An `include` block isn't producing the merged config you expected. - A child unit's `inputs` map seems to keep parent keys you tried to drop. - A `dependency` block's `mock_outputs` produces values the actual upstream never emits. - `terragrunt run --all apply` is on the table for a production rollout. - A `terragrunt.stack.hcl` file is in the repo and you need to know how it generates units. - Hooks (`before_hook`, `after_hook`, `error_hook`) fire at the wrong moment or silently swallow errors. ## Cross-cutting rules These layer on top of `terraform-workflows` cross-cutting rules. Plan-then-apply, never bump pins in passing, never `-auto-approve` on shared state — all of those still apply. 1. **Treat the CLI redesign as the default.** Even if a repo still uses `run-all` and `--terragrunt-*` flags, write new code in the new form (`run --all`, `--<flag>`, `TG_*` env vars). Set `TG_STRICT_CONTROL=cli-redesign` locally so you can't accidentally regress. 2. **`run --all <mutation>` requires a plan-aggregation step.** It does NOT produce a unified plan.