spring-projects / spring-projects/spring-vault
Request: Retry mechanism for vault template
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 306
- Forks
- 202
- PR merge metrics
- No merged PRs in 30d
Description
Hi 👋
I saw this first asked in stackoverflow.
This seems fairly common and a normal thing to have (retries) but all the alternatives to implement this are very cumbersome.
With the advent of service meshes I believe this will become even more necessary as a common issue when using these are race conditions between our Spring application and the service mesh proxy which can cause the Spring app to fail to start.
I think having something like spring.cloud.vault.something.retries=3 would be a more convenient way to do this and a much welcomed feature by users of Spring Vault.
I'm happy to draft a pr if there is interest.
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
Start with the linked Stack Overflow discussion and inspect how Spring Vault currently handles startup access to Vault. The issue does not name files, tests, or entry points; done would mean an agreed retry configuration for Vault template startup failures, with its behavior documented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100