Add built in Hashicorp vault resolver
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 34
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The vault CLI is huge, and what's needed to retrieve secrets is just a simple HTTP request. It's not great having to add that CLI to a Docker image in order to use nv in containerized apps. Given vault's popularity, this seems like a good candidate to add as a built-in resolver.
Some research is needed of the common authentication methods supported by vault, to better understand which ones are best to start with and to anticipate how complicated supporting vault natively could become.
Contributor guide
No contributing guide indexed for this repository
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 researching Vault's common authentication methods and how a native HTTP-based resolver would fit the project. Done means a defined, appropriately scoped built-in Vault resolver can retrieve secrets without requiring the Vault CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100