-
Use eureka.instance zone data consistently determining client zone · 6087bc75Dave Syer authored
The zone for a remote server comes from its eureka.instance.metadataMap.zone, but we didn't (until this change) apply the same logic to the client. If the client is registering itslef with eureka then it will have a metadataMap itself and we should be able to just reverse the logic. Fixes gh-991
6087bc75
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| eureka | Loading commit data... | |
| ribbon/eureka | Loading commit data... |