Refresh configuration without restart, but behind load balanced URL

I am currently using Steeltoe in an environment which is behind a load balanced URL, and looking for a means to refresh the configuration without restarting. The load balancer directs traffic to several different Cloud Foundry environments, each of which could have 1 to many instances of the app running via autoscaler.

I’ve read through previously reported issues and noted this issue which mentions IOptionsSnapshot and the /reload endpoint, as well as IConfigurationRoot.Reload. Based on my current understanding, Steeltoe users with a similar load balanced environment may have an issue with finding a way to reload configs across all environments, for all app instances, as a call to the /reload endpoint would only hit a single environment/instance. Hopefully I am overlooking a solution to this issue.

If not, I noticed that perhaps the ideal solution is in the backlog. I am not intimately familiar with the Steeltoe source code yet, but is this a feasible addition, or is this a serious undertaking? I would love to help contribute to implementing this, but thought I would first check if others have looked into it already and noticed significant blockers.

[TimHess]

@antonpopov I’m so sorry, I thought I responded to this message last week - this is still on the roadmap, but Bus builds on Streams, which builds on Messaging…

We’re pretty confident that Messaging is ready for consumption, and a good chunk of the Streams work is there now, but Bus hasn’t been started. So we’ve made progress, but we’re not there yet

[antonpopov]

@TimHess do you plan on implementing this feature anytime soon? My team is using Steeltoe’s refresh actuator which works good but soon we are starting a project where microservice instances will self register to a Netflix Eureka discovery server. Would you suggest an approach for refreshing the configuration of multiple instances of a microservice. Thanks!