v1.4.0

• Consul config change: adding 'acl_enforce_version_8: false' needed before we upgrade to 0.8.x (or we need to update our policies https://www.consul.io/docs/guides/acl.html#complete-acl-coverage-in-consul-0-8). Run update-consul-config to apply this config change before the new Consul AMI is deployed Nike-Inc/cerberus-consul-puppet-module#10

v1.3.0

• Updated IAM Role permissions for the Consul IAM role to allow for a more robust Upstart script. Consul now only attempts to send CloudFormation success signals when a create or update event is occuring.

v1.2.0

• Adds view-config command to view config files stored in S3
• Adds update-cms-config to update the CMS environment properties file in S3
• Fixes bad Consul config from version 1.1.0 of the CLI

v1.0.0

• Adding performance settings recommended for Consul 0.7.x or newer
• Setting skip_leave_on_interrupt=false to prevent Consul servers from being marked as 'failed' during rolling update (skip_leave_on_interrupt defaults to true for servers 0.7.x or newer)
• These changes are not compatible with Consul 0.6.4.

After upgrading Consul to 0.7.x or newer, run the update-consul-config command to apply settings needed for Consul 0.7.x or newer.

v0.19.0

• Parameterized PauseTime and WaitOnResourceSignals for CloudFormation AutoScalingRollingUpdate
• Added option to update-consul-config so user can supply ACL Master Token and Gossip Encryption Token

v0.18.0

• Adding command for that updates the consul configuration for the cluster while maintaining the secrets in the current config. (FYI: the version of consul configuration currently bundled in CLI is compatible with Consul 0.6.4)
• Updating CloudFormation to keep the min number of instances in service while doing updates (e.g. if you have 3 instances, add a new instance and wait for it to be healthy before removing one of your original 3 instances). This should be a safer way to update Vault and Consul.

v0.17.0

• cms and gateway to use cf signals and required policy changes

v0.16.3

• Exit with failure code when update stack does not succeed.

v0.16.1

• Partially fix a bug were we assumed all data was Map<String, String> it turns out you can add any valid JSON data type into Vault as a value.

v0.16.0

• Cutting a release so that the cli version matches the release version