Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't restart on configuration change #72

Closed
dpetzel opened this Issue Oct 30, 2014 · 0 comments

Comments

Projects
None yet
1 participant
@dpetzel
Copy link
Contributor

dpetzel commented Oct 30, 2014

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?

johnbellone added a commit that referenced this issue Nov 3, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.