v0.11.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

• #234

v0.10.1

Modules affected

• consul-cluster

Description

• You can now configure lifeycle hooks on the ASG created by the consul-cluster module using the new lifecycle_hooks input variable.

Special thanks

• Thank you to @mr-miles for the contribution!

Related links

• #223

v0.10.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

• #225

v0.9.3

Modules affected

• install-consul

Description

• Update install-consul to detect the CPU architecture type (e.g., amd64, arm64, etc) and automatically install the appropriate Consul binary for that architecture.

Special thanks

• Thank you to @izzyleung for the contribution!

Related links

• #222

v0.9.2

Modules affected

• consul-security-group-rules

Description

• Fix a bug where the consul-security-group-rules module couldn't handle an empty allowed_inbound_cidr_blocks list.

Special thanks

• Thank you to @mr-miles for the contribution!

Related links

• #218

v0.9.1

Modules affected

• setup-systemd-resolved

Description

• We are now testing this repo with Ubuntu 20.04. Other than updates to docs, examples, and tests, the only change to a module required to make the code work was an install check in the setup-systemd-resolved module. There should be no change to behavior / functionality.

Special thanks

• Thank you to @mpluhar for the contribution!

Related links

• #217

v0.9.0

Modules affected

• consul-client-security-group-rules
• consul-cluster
• consul-iam-policies
• consul-security-group-rules
• install-consul
• install-dnsmasq
• run-consul
• setup-systemd-resolved

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

• #216

v0.8.6

Modules affected

• install-consul

Description

• Fix a bug in how install-consul checks that the consul binary was installed correctly to handle the case where the install dir has restricted permissions.

Special thanks

• Thank you to @yardbirdsax for the fix!

Related links

• #214

v0.8.5

WARNING: This release may be backwards incompatible with Consul versions before 1.9.0. We should've bumped the version number to v0.9.0, but it's too late to do that now. See #220 for more details.

Modules affected

• run-consul

Description

• Update the run-consul script to set two configs differently: first, we set disable_compat_1.9 = true in telemetry and second, to enable the UI, we set a ui_config block instead of the old ui attribute.
• Update all Consul examples and automated tests to use Consul 1.9.2.

Related links

• #208

v0.8.4

Modules affected

• consul-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

• #207