StackGuardian / StackGuardian/tirith
research(core): state ↔ plan correlation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
"This plan reverts a console change", "this resource is managed by two states" — drift-aware
policy, the one thing static analysis is structurally incapable of. Falls out of named multi-input
plus a terraform_state reader; no separate engine work.
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
The issue names named multi-input and the terraform_state reader as the starting points; read those entry points first to determine how plan/state correlation is represented. Done means defining drift-aware policy support for correlating a plan with state, without separate engine work; no file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- terraform
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100