StackGuardian / StackGuardian/tirith
feat(compat): Terragrunt support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
terragrunt show -json (and terragrunt plan -out + show) should produce the same plan document
the terraform_plan provider reads — verify against a real Terragrunt project, document the flow,
and add a fixture. The real work is run-all: one invocation yields one plan per module, so Tirith
needs a documented pattern (and, if cheap, a small helper) to evaluate each plan and aggregate exit
codes — worst-verdict-wins, per-module addresses in the output. The R4 wrapper-mode issue gains a
terragrunt variant.
Acceptance. Docs section with a run-all recipe; a Terragrunt-produced plan in the test
fixtures; exit-code aggregation covered by a test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the terraform_plan provider and the R4 wrapper-mode handling, then inspect the existing test fixtures and exit-code tests. Add the documented Terragrunt run-all recipe, a Terragrunt-produced plan fixture, and coverage showing worst-verdict-wins aggregation with per-module addresses.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, documentation, infrastructure, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100