spring-cloud / spring-cloud/spring-cloud-commons
Common discovery properties
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 751
- Forks
- 744
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Eureka, consul and zookeeper have very similar properties for things like hostname, ipaddress, port, preferIpAddress, service or app name, instance id, metadata, etc...
It may be worth having a common set of properties under spring.cloud.discovery and then each can have custom properties.
It may be that this is just an abstract class and downstream projects use spring.cloud.<project>.discovery as namespace.
Maybe migrate netflix from eureka.instance to spring.cloud.netflix.discovery.
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 proposes common discovery properties under spring.cloud.discovery for Eureka, Consul, and Zookeeper, with possible Netflix migration. Start by comparing the existing discovery configuration properties in those implementations. Done would require an agreed common abstraction and namespace strategy, plus any required migration, but the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- cloud, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100