We are trying to move away from un-versioned REST endpoints like "/reload" in favor of versioned endpoint(s) that take calls. We don't have a good story yet for endpoints that are not hosted by Master and Agent actors. So, at first blush, I'm wary of this solution.
- Why not scan the config directory every time? Are you trying to avoid the > speed hit from disk reads? > Why not do this? If a network config doesn't exist in memory, refresh configs by reading from disk and check again; basically acting like a cache. Seems straight forward enough?
