resolve endpoint zone from metadata

[MI-cool]

endpoint zone can be get from metadata

[troshko111]

The change LGTM, but can you elaborate on the bug and add some tests showing how it fixes it?

[MI-cool]

Sorry.
My project was build with spring-cloud-starter-netflix-eureka-client.
I use the following configuration to make the client dynamically aware of the server nodes.

eureka.client.transport.bootstrapResolverStrategy=composite
eureka.client.transport.readClusterVip=eureka-read-server
eureka.client.transport.writeClusterVip=eureka-write-server

During the test, it was found that the client lost the server zone information. Finally found that the more reasonable way to modify is to add a few lines of code submitted.

[MI-cool]

I will try to add some tests.

[MI-cool]

Test was done.

[troshko111]

Sorry for the delay, this fell off my attention, I promise to have a short turnaround now.
I looked around the code and seems like this is Aws-specific path (see the return type) so it's expected to not to have the zone info on MyDatacenterInfo, there's no contract saying there should be any zone there in the meta. What issues it this causing?

[MI-cool]

My eureka server was build with spring-cloud-starter-netflix-eureka-server. On server side, the framework build instances use dataCenterInfo type of MyDataCenterInfo as default.
My eureka client was build with spring-cloud-starter-netflix-eureka-client. I use eureka.client.transport.bootstrapResolverStrategy=composite to make the client dynamically aware of the server nodes. Here comes the problem, since newBootstrapResolver lost zone of server instances, eureka clients can't be zone affinity to server instances.

[troshko111]

Yeah I think this is reasonable, the current AWS/non-AWS separation is weak so I don't see a better place to do this tbh. Thanks and sorry for the delay.

[MI-cool]

No worries.