Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Releases: hashicorp/terraform-aws-nomad

v0.4.3

24 Aug 22:33
Compare
Choose a tag to compare

651ee4e: Fix the AWS account we use for publishing the public example AMIs.

v0.4.2

30 May 16:28
4b12b17
Compare
Choose a tag to compare

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

v0.4.1

05 May 23:52
528b8e5
Compare
Choose a tag to compare

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

v0.4.0

09 Apr 23:47
9964c7e
Compare
Choose a tag to compare

#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

27 Mar 23:21
9b90bfd
Compare
Choose a tag to compare

#25: Update examples to use HTTPS URLs instead of Git URLs.

v0.3.0

14 Mar 11:06
01f5f76
Compare
Choose a tag to compare

#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

28 Feb 12:40
364c7a7
Compare
Choose a tag to compare

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

v0.1.1

17 Feb 00:44
9f49300
Compare
Choose a tag to compare

#22: You can now specify a custom name for the Nomad ASG using the asg_name parameter.

v0.1.0

30 Jan 23:51
df4061b
Compare
Choose a tag to compare

#17: Update versions of Nomad and Consul.

v0.0.5

14 Dec 13:49
33a6757
Compare
Choose a tag to compare

#14: You can now attach additional security groups to the EC2 Instances using the security_groups param in nomad-cluster.