spring-cloud / spring-cloud/spring-cloud-config
Using both Consul KV and Vault backend
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
In my project, I am storing configuration in Vault. Recently, I plan to store plain configurations in Consul KV and secret configurations such as DB username/password, API key... in Vault.
I think Backend for Consul KV should be added to Spring Cloud Config Server so I can use both Consul KV and Vault as Composite Environment Repositories.
Thank you
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
The issue names no files or tests. Start by locating the existing Vault backend and composite environment repository implementations, then examine how a Consul KV repository would fit alongside them; done means Spring Cloud Config Server can use Consul KV and Vault together as composite repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100