spring-cloud / spring-cloud/spring-cloud-config
Connect to Multiple Vault Secrets Engines
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Since Vault allows for multiple secrets engines, it seems reasonable to expect that one might use multiple engines for the same project. For example, Vault supports database secrets engines that manage, well, database secrets, but many other properties will just be key-values. It would be nice to pass a list of secrets engines into the "backend" property rather than it just accepting a single secrets engine.
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
The issue names no files or tests; start by tracing how the Vault backend property is parsed and how the current single secrets engine is selected. Review the existing Vault integration and define done as supporting a list of engines for one project while preserving current single-engine behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100