Hmm..We are not doing yet, but are planning on using traffic_ctl to update our ssl certs etc soon and I was hoping to use “status” as a means to ensure if there’s any pending update that hasn’t been applied or also as a means to confirm that the last “reload” was completed successfully.
Is there any alternate planned for status if we are thinking about removing it? Even if it doesn’t tell which specific config need to be reloaded, it seems like it’s still got some value. - Sudheer > On Oct 10, 2019, at 3:34 PM, Fei Deng <duke8...@apache.org> wrote: > > While fixing the problem where "remap.config" gets reloaded automatically, > we noticed it is related to the command "traffic_ctl config status". Some > of us at the summit thinks that this command isn't useful, since the only > thing it does is returning a status code to say some config files has been > changed and a "traffic_ctl config reload" is required to make those changes > take effect. However, it does NOT show which of the config files has been > changed. > > So we're proposing to remove this command, since it doesn't really do > anything, and since it's run on a seperate thread by itself (check file > changes and sleep for 1 second), we can also remove that thread as well.
