Doesn't restart on configuration change

[dpetzel]

I'm not sure if this is by design or not, so feel free to close if it is.

I noticed today that when you apply a new configuration, the consul service is not restarted. Specifically in my case today, I had originally spun up the service using all the defaults and found the service was listening on 127.0.0.1. So i then set node.default[:consul][:bind_addr] = '0.0.0.0' and re-ran Chef. The configuration file on disk was updated, but the service didn't get restarted. Thoughts on adding a notifies :restart, "service[consul]" to the configuration file resource?

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.