v0.3.5

#66: You can now use the --environment option with the run-consul script to set environment variables that should be exposed to Consul in its supervisord config.

v0.3.4

#65: Remove provider and aws_region from examples so you can use them following the instructions in the Terraform Registry.

v0.3.3

#59: The Security Group rules that open up ports for Consul Agents in client mode (that is, the ports for lan gossip) have been extracted into a new consul-client-security-group-rules module. This allows you to attach those rules to any Security Group that has Consul clients on it (e.g., Vault). The original consul-security-group-rules module includes the new consul-client-security-group-rules, so existing deployments should be unaffected.

v0.3.2

#58:

• The install-consul script now exposes the --ca-file-path, --cert-file-path, and --key-file-path options to make it easier to install TLS certs.
• The run-consul script now exposes --enable-gossip-encryption and --gossip-encryption-key options to make it easier to enable gossip encryption.
• The run-consul script now exposes --enable-rpc-encryption, --ca-path, --cert-file-path, and --key-file-path options to make it easier to enable RPC encryption.

v0.3.1

#56: The consul-cluster module will now apply a Name tag, set to var.name, to the Consul security group.

v0.3.0

#57:

BACKWARDS INCOMPATIBLE CHANGE

The consul-cluster module no longer supports the target_group_arns and load_balancers parameters. Instead, to associate a load balancer with your Consul cluster, you should use a separate aws_autoscaling_attachment resource. See docs here.

Note that to deploy this change without downtime, you will most likely want to spin up a new Consul cluster (new ASG), using the same tags and load balancer (but this time with the aws_autoscaling_attachment resource), wait for it join the original cluster, and then tear down the old ASG.

v0.2.2

#50: You can now specify a custom data center configuration for Consul by setting the --datacenter option when calling run-consul.

v0.2.1

#45: You can now use Spot Instances in your Consul cluster by setting the spot_price parameter. Also, updated the run-consul script to retry its search for EC2 Tags if none are found, as Tags can sometimes take a while to propagate.

v0.2.0

#48:

BACKWARDS INCOMPATIBLE CHANGE

The Consul ASG is now namespaced using the cluster_name variable, just like all the other resources. Terraform treats renaming an ASG as deleting the old one and creating a new one, so be careful when updating!

Probably the best option is to:

1. Add a second consul-cluster module to your code but with the same cluster_tag_key and cluster_tag_value as the first cluster.
2. Run terraform apply.
3. This will bring up a second ASG that should be part of the same Consul cluster as the first. Wait for all the new nodes to come up, sync with the original nodes, and replicate the data.
4. SSH to each of the nodes in the old ASG and call consul leave on each node to have it leave the cluster.
5. Remove the old consul-cluster module from your code.
6. Run terraform apply.
7. Now you're left with just the new cluster.

As always, make sure to test this in a pre-prod environment before prod!

v0.1.2

#47: You can now specify custom tags for the Consul cluster using the tags parameter.