v188

Final release 188

v187

Final release 187

v186

Final release 186

v185

Final release 185

v184

Final release 184

v183

Final release 183

v182

Final release 182

v181

NOTABLE NEW FEATURE:
Confab will not insert consul.encrypt_keys into consul's keyring if they have not changed. Particularly in large deployments, the key insertion can take several minutes (see v179, where the timeout for this was made configurable as confab.timeout_in_seconds). Now you should only see issues with timeouts or full disks leading to the message X/Y nodes reported success in logs when you are intentionally rotating the encrypt keys, in which case, you will still need to redeploy with a longer timeout or find the root cause of the issue.

v180

BUG FIXES:
On windows, we were not handling servers with multiple DNS servers set. Until now.

v179

NOTABLE NEW FEATURE:
The timeout for the overall job has been made configurable as confab.timeout_in_seconds. By observing the resolution of a production issue in Pivotal Web Services with Pivotal's Cloud Operations team we were able to determine that consul's gossip key insertion can take several minutes to complete in large scale deployments. This timeout allows consul_release to be tolerant of this. If you encounter the X/Y nodes reported success message in your logs when deploying consul, you should consider enlarging this timeout by a factor of 2.