spring-cloud / spring-cloud/spring-cloud-vault
Config Server + Config Vault + Actuator = two beans with the same name
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 291
- Forks
- 152
- Avg merge
- 11h 24m
- Merged PRs (30d)
- 3
Description
When we have
spring-cloud-config-server, spring-cloud-starter-vault-config and starter-actuator on the classpath we get the issue that the bean vaultTemplate is defined in SpringVaultClientConfiguration and in VaultAutoConfiguration. The application will not start unless we provide bean overriding.
It's enough to rename one of those beans to fix this.
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 inspecting SpringVaultClientConfiguration and VaultAutoConfiguration, where the duplicate vaultTemplate beans are defined. Reproduce the startup failure with spring-cloud-config-server, spring-cloud-starter-vault-config, and starter-actuator on the classpath. Done means the application starts without enabling bean overriding and only one bean name remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100