spring-projects / spring-projects/spring-vault
Spring Vault should raise an event after properties have been updated due to secret rotation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 306
- Forks
- 202
- PR merge metrics
- No merged PRs in 30d
Description
Problem: Currently it is awkward to update relevant beans with updated properties when the secret lease has been rotated.
Proposed solution: LeaseAwarePropertySource can raise an event (e.g. AfterSecretLeaseRotatedEvent) with the changed properties, so that relevant beans can implement a listener to this event to update themselves.
Note: This enhancement request was originally reported at https://github.com/spring-cloud/spring-cloud-vault/issues/742
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 by locating LeaseAwarePropertySource and tracing how secret lease rotation updates properties. Define the event contract, including the changed properties, and determine how relevant beans can listen for it. Done means property updates after rotation emit an AfterSecretLeaseRotatedEvent that listeners can use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend-api-design, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100