These are chat archives for spring-cloud/spring-cloud
turbine.instanceInsertPort=false. Dunno if that's the best way but it did the trick
@FeignClients that share the same name and have fallbacks
Our scenario is we have a "products" service, that manages templates for ecommerce products. But it also has the concept of a "catalog". To keep the interfaces not quite so burly, we have 2 different feign clients. Both work fine, until you introduce the fallbacks. Digging through the guts, it looks like the Registrar creates a map via the specified name, so only 1 of the clients will have it's configs analyzed an instantiated.
But when the
FeignClientFactoryBean.HystrixTargeter tries to fetch the fallbackInstance, it can't find it for the entry that got overridden in the map. We tried using a different name and specifying the URL, but that prevents the load balancer / discovery from being picked up :(