Releases: hashicorp/terraform-aws-nomad
v0.4.3
v0.4.2
v0.4.1
v0.4.0
#27:
-
Update Consul usage to v0.3.1 everywhere. Consul has some backwards incompatible changes, so please check the release notes before upgrading.
-
Update all Git URLs to use HTTPS instead of SSH for consistency.
-
Fix tags set on Nomad cluster in root example. Nomad clients should not get the same tags as servers.
v0.3.1
v0.3.0
#23:
BACKWARDS INCOMPATIBLE CHANGE
The nomad-cluster
module no longer supports the target_group_arns
and load_balancers
parameters. Instead, to associate a load balancer with your Nomad 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 Nomad 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.0
#24:
BACKWARDS INCOMPATIBLE CHANGE
To be more consistent with the Consul module, the nomad-cluster
module now takes as input a cluster_tag_value
parameter that will be used to tag the instances for auto-discovery. If you are updating from a previous of the nomad-cluster
module and want to maintain backwards compatibility, you should add the cluster_tag_value
parameter and set it to the same value as the cluster_name
parameter.