stackql / stackql/stackql-devel
[FEATURE] Mature secret system
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Feature Description
We need a system for secrets management that:
- has a default local implementation.
- integrates secrets engines such as Hashicorp Vault on an opt-in basis.
Example(s)
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Possible Approaches or Libraries to Consider
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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 surveying the repository for existing secret-handling code and configuration, then define the scope for a default local implementation and opt-in HashiCorp Vault integration. Done should include an agreed design and working implementations for both paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100