Secret references
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Parent: #207
Summary
List all managed secrets by name/ARN without exposing values. Customers already have access to their cloud provider secret stores — this tells them what to look for.
Requirements
- Extract secret resource references from Pulumi state (AWS Secrets Manager secrets, Azure Key Vault secrets)
- Write
secrets/secret-references.jsonwith fields:name,arn_or_id,purpose,stack - Include license secret(s) with a note on how to update
Acceptance Criteria
secret-references.jsonlists all managed secrets with enough context for the customer to look them up- No plaintext secret values in the bundle
Leaving this open based on the PR comments. Current implementation won't automatically reflect secret schema changes.
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 examining the Pulumi state for AWS Secrets Manager and Azure Key Vault secret resource references. Produce secrets/secret-references.json with name, ARN or ID, purpose, and stack, including license secrets and update guidance. Done means the bundle reflects schema changes and contains no plaintext secret values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100