v0.10.0

Description

• Terraform 1.0 upgrade: We have verified that this repo is compatible with Terraform 1.0.x!
  • From this release onward, we will only be running tests with Terraform 1.0.x against this repo, so we recommend updating to 1.0.x soon!
  • To give you more time to upgrade, for the time being, all modules will still support Terraform 0.15.1 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 1.0.x.

Related links

• #101

v0.9.1

Modules affected

• install-nomad

Description

• The install-nomad script now supports ARM processors!
• Updated the examples in the examples folder to include ARM, as well as bumping the default Nomad version to 1.1.1 and default Consul version to 1.9.6.

Special thanks

• Thank you to @nepeat for the contribution!

Related links

• #97

v0.9.0

Description

• Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
  • From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
  • To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
  • Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.

Related links

• #95

v0.8.0

Description

• Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
  • From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
  • To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
  • Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.

Related links

• #94

v0.7.2

Modules affected

• nomad-cluster

Description

• Fix a bug where nomad-cluster wouldn't handle an empty allowed_ssh_cidr_blocks input correctly.
• You can now configure the allowed outbound CIDR blocks via the new allow_outbound_cidr_blocks input variable.

Special thanks

• Thank you to @MatthiasScholz for the contribution!

Related links

• #85

v0.7.1

Modules affected

• nomad-cluster

Description

• You can now configure a permissions boundary for the IAM role using the new iam_permissions_boundary input variable.

Special thanks

• Thank you to @guangie88 for the contribution!

Related links

• #87

v0.7.0

Modules affected

• (none)

Description

• Terraform 0.13 upgrade: We have verified that this repo is compatible with Terraform 0.13.x!
  • From this release onward, we will only be running tests with Terraform 0.13.x against this repo, so we recommend updating to 0.13.x soon!
  • To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.13.x.
  • Once all Gruntwork repos have been upgrade to work with 0.13.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.

Related links

• #81

v0.6.7

Modules affected

• nomad-cluster

Description

• The nomad-cluster module now provides output variables with information about the IAM instance profile: iam_instance_profile_arn, iam_instance_profile_id, and iam_instance_profile_name.

Special thanks

• Thank you to @nicgrayson for the PR!

Related links

• #72

v0.6.6

Modules affected

• nomad-cluster

Description

• The nomad-cluster module now sets the ignore_changes lifecycle setting on load_balancers and target_group_arns attributes. As of AWS Provider 3.x, if you use aws_autoscaling_attachment, you MUST have ignore_changes set on these attributes, or your load balancer will be removed (see corresponding issue in the AWS provider). Since the nomad-cluster module doesn't let you use these attributes anyway, this should be a backwards compatible change that allows this module to work properly with a load balancer.

Special thanks

• Thank you to @so-development for the PR!

Related links

• #78

v0.6.5

Modules affected

• nomad-cluster

Description

• Set default values for availability_zones and subnet_ids to null in nomad-cluster. As of AWS Provider 3.x, only one of these parameters may be set at a time on an Auto Scaling Group, so we now have to use null rather than empty list as our default.
• Update all examples to use v0.7.7 of terraform-aws-consul, which has a similar fix to work with AWS Provider 3.x.

Related links

• #73