Update to consul.json does not trigger service restart

[errygg]

Had to update the node name to the hostname to support our deployment, but when the node name (i.e. node['consul']['config']['node_name']) attribute was overridden, it did not restart the consul service. Had to manually restart to capture the new node name.

Running on ubuntu jessie with chef client version 12.16.42.

[legal90]

Hi, @errygg
This issue duplicates #307 and #341

Service restart was disabled intentionally by 80f4a1c and #309
Please, refer to the discussion: #288

TL;DR: Automatic restart of Consul servers could cause a cluster downtime when you run chef-client simultaneously on your nodes. Also, if Consul version has been changed (upgrade scenario), then Consul servers should be restarted manually, according to the upgrade manual.

[errygg]

Thanks @legal90! I guess I wasn't the first to see this. I'll go ahead and close the issue out. Automate all the things (except consul restarts 😆 )

[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.