StackGuardian / StackGuardian/tirith
research(provider): `terraform_code` — an HCL source provider
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
Some things are structurally absent from plan JSON: backend config, lifecycle meta-arguments
(prevent_destroy, ignore_changes, create_before_destroy), moved/import/removed blocks.
Only an HCL provider reaches them. Measured demand from public check libraries is small (a couple
dozen checks); the strategic value is running Tirith instead of a static scanner, plus in-code
suppression comments and editor tooling. Reuse conditions and eval_expression unchanged. Decide
after R3.
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
No files, tests, or entry points are named. Start by reviewing the R3 decision and the existing provider architecture; done means a decided scope for an HCL source provider covering the listed Terraform constructs, rather than an implementation target stated in this issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100