spring-cloud / spring-cloud/spring-cloud-vault
Auto reload secrets from vault
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 291
- Forks
- 152
- Avg merge
- 11h 24m
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
We are adding in some services secrets over time, and we need to restart the service/or refresh the context externally via actuator endpoint, after updating the secrets in vault. Introducing a auto reload mechanism would improve the workflow.
Describe the solution you'd like
Integrating the hashicorp/vault documenteted solution natively into the spring-cloud-vault-config library. Maybe with additionally checking if the secret version has changed.
Describe alternatives you've considered
Implementing it myself into services/creating a company wide library to realize this feature.
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 with the spring-cloud-vault-config library and the linked HashiCorp Vault Spring reload documentation. Review how the library currently obtains secrets and how actuator refresh is used externally. Done means secrets update automatically after changes in Vault, potentially by detecting a changed secret version, without restarting the service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100