spring-cloud / spring-cloud/spring-cloud-consul
Allow for consul services to be used as configuration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 822
- Forks
- 539
- Avg merge
- 9h 31m
- Merged PRs (30d)
- 7
Description
When services are registered as consul services, the service has several properties that can be queried via consul APIs. For example a MongoDB registered service has an Address, Port, Tags as part of the consul service.
The current configuration of endpoints for Spring Cloud applications is hardcoded in Consul K/V store. But some of these (see examples in http://docs.spring.io/spring-boot/docs/current/reference/html/common-application-properties.html) can be Consul services, not hardcoded non-moving parts.
Allow for using Consul services as application configuration.
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 reviewing how Spring Cloud applications currently obtain endpoint configuration from the Consul K/V store, then compare that with the Consul service properties described in the issue: Address, Port, and Tags. Use the linked Spring Boot application-properties reference for examples of endpoint settings. Done should mean application configuration can use registered Consul services rather than only hardcoded K/V values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100