StackGuardian / StackGuardian/tirith

research(core): state ↔ plan correlation

Open
#350 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

research
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.