StackGuardian / StackGuardian/tirith
feat(terraform_plan): expose `action_reason`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
Terraform emits replace_because_cannot_update, replace_because_tainted, replace_by_triggers,
delete_because_no_resource_config, delete_because_count_index; Tirith reads actions and
ignores it. delete_because_no_resource_config is "a module was removed and it destroys
production", named precisely at plan time. Not present in older fixture plans — confirm against a
fresh Terraform version first. Turns a verdict into an explanation.
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 by checking Tirith's handling of Terraform plan actions, then generate a plan with a fresh Terraform version to confirm the available action_reason values. Compare this with older fixture plans and trace where the actions field is read. Done means the relevant action_reason is exposed as part of the verdict explanation without breaking plans that lack it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, terraform
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100