spring-cloud / spring-cloud/spring-cloud-vault
Confusing documentation on how to configure databases
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 291
- Forks
- 152
- Avg merge
- 11h 24m
- Merged PRs (30d)
- 3
Description
Describe the bug
When upgrading to version 3.1.0 I noticed that the bootstrap.yaml file wasn't read anymore. I then moved the content to application.yaml and noted that the integration with vault started to work, but not the database config. Looking at the documentation didn't give me any insight in how this was supposed to be solved.
In the end I resorted to add a dependency to spring-cloud-starter-bootstrap and move back the config to bootstrap.yaml. This working.
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 comparing the documented database configuration with the behavior described for bootstrap.yaml and application.yaml in Spring Cloud Vault 3.1. Review the configuration documentation and relevant upgrade guidance first; this is done when the supported placement, required dependency, and database setup are clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100