[FEATURE] Mature secret system

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
security

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.

Description

enhancement v0.4

Feature Description

We need a system for secrets management that:

  1. has a default local implementation.
  2. 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.

Dominant language
Go
Stars
0
Forks
0
No merged PRs in 30d

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.

More from stackql/stackql-devel

All issues in stackql/stackql-devel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.