spring-cloud / spring-cloud/spring-cloud-vault
Use versioning (Key Value backend v2) features for configuration properties
Open
Nobody has claimed this yet.
status: declined
type: enhancement
- Dominant language
- Java
- Stars
- 291
- Forks
- 152
- Avg merge
- 11h 24m
- Merged PRs (30d)
- 3
Description
We should investigate how and whether it makes sense to use Vault's versioning features to consume older versions of secrets through the versioned Key-Value backend.
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
Start by examining the configuration properties integration and the versioned Key-Value backend referenced in the issue, then investigate Vault's versioning features and how older secret versions could be consumed. Done means the repository has a clear decision on whether this fits, with the required scope and implementation approach documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100