StackGuardian / StackGuardian/tirith
feat(terraform_plan): `referenced_by_filter` + `referenced_by_attribute` on `direct_references`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
A left-join read: "the bucket's policy resource has this attribute", "the LB listener that
references this target group uses HTTPS" (ALB HTTP→HTTPS, WAF protection, keyvault/apigateway
pairs). The miss must be padded as a None value, not ProviderError(severity 2) — an
unmatched left row is the normal state of a left join, and severity-2 routing makes the
skip hazard the default shape of every such policy. Address handling must module-qualify the target
(a naive helper produces edges that can never match inside modules) and must not strip count
indices (fails closed N×M). Depends on the nested-expressions walker and the R1 skip-ordering fix.
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 at the direct_references entry point and read the nested-expressions walker and the R1 skip-ordering fix it depends on. Trace how left-join misses, module-qualified addresses, and count indices are represented; done means the new filters support these cases without turning unmatched rows into ProviderError results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, terraform
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100