spring-cloud / spring-cloud/spring-cloud-config
Support Vault health endpoint in health check
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Problem
If a Vault token is not provided to the Config Server when accessing it's health actuator then the Vault backend health check will respond as failed.
Requested Solution
If a Vault token is not provided, the Config Server health check should not fail and may provide just the Vault server's health status API response instead.
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 at the Config Server health actuator and review the Vault backend check against Vault's System Health API documentation. Verify the behavior when no Vault token is provided and define the response using the requested endpoint semantics. Done means the health check no longer fails solely because the token is absent and exposes the Vault server health status appropriately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100