Asgard is unable to talk to a Eureka that has no urlContext

[cquinn]

We've setup our Eureka instance at the ROOT context in tomcat. So its url looks like hostname:8080/v2/... . There is no (redundant) 'eureka' in the url.

Setting Asgard's eureka.urlContext to '' in theory should work, but the code in Asgard treats null/blank as "use default" and uses '/eureka' instead.

There should be a way to indicate that a "no context" url us really desired.

[joesondow]

Yup. I always wondered if this idea would come up. Carl, are you going to assign this to yourself and make the no-context option possible?

Hint: Add more logic in DiscoveryService.findBaseUrl (or EurekaService if it gets renamed), and also ConfigService.getEurekaUrlContext