v0.4.0

Modules affected

• executable-dependency
• instance-type
• join-path
• list-remove
• operating-system
• prepare-pex-environment
• request-quota-increase
• require-executable
• run-pex-as-data-source
• run-pex-as-resource

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.
• Remove docker key from machine config
• Add placeholder.tf for TFC/TFE/PMR
• Lock PIP's version to be smaller than 21.0

Related links

• #36
• #37
• #41
• #40

v0.3.2

Modules affected

• request-quota-increase

Description

• CircleCI improvements: Fix CircleCI Contexts and switch from Dep to Go Modules
• [NEW MODULE] Request quota increase for an AWS resource

Related links

• #33
• #35
• #34

v0.3.1

Modules affected

• executable-dependency

Description

Fix OS permissions that are set on the downloaded binary from the executable-dependency module.

Related links

• #32

v0.3.0

Modules affected

• executable-dependency
• instance-type
• join-path
• list-remove
• operating-system
• prepare-pex-environment
• require-executable
• run-pex-as-data-source
• run-pex-as-resource [BACKWARDS INCOMPATIBLE CHANGES]

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.
• The run-pex-as-resource module no longer supports running code on destroy. See the migration guide below for more details.

Migration guide

• The run-pex-as-resource module will no longer run your executable on destroy. We had to drop this (rarely used) functionality due to a backwards-incompatible change in Terraform 0.13 to destroy-time provisioners.
• If you were depending on this behavior, you will need to find an alternative, such as creating a custom Terraform provider.
• You can no longer pass the following input params to the run-pex-as-resource module:
  • destroy_command_args
  • enable_destroy_provisioner

Related links

• #30

v0.2.1

Modules affected

• instance-type [NEW MODULE]

Description

• Added a new instance-type module that can tell you which of a list of instance types are available in all AZs in the current AWS region.

Related links

• #29

v0.2.0

Modules affected

• enabled-aws-regions [REMOVED]

Description

enabled-aws-regions has been removed as there is now a new data source in the aws provider that has the same functionality. Replace usage of the module with the aws_regions data source

Related links

• #27

v0.1.8

Modules affected

• executable-dependency [NEW MODULE]

Description

• Added a new module called executable-dependency that can be used to install an executable if it's not installed already. This is useful if your Terraform code depends on external dependencies, such as terraform-aws-eks, which depends on kubergrunt.

Related links

• #28

v0.1.7

Modules affected

• operating-system

Description

• Fully rely on Python to determine the path separator. This is an internal refactor to make the code cleaner and safer and should have no impact on external behavior.

Special thanks

• Thanks to @maxbrunet for the PR!

Related links

• #26

v0.1.6

Modules

• run-pex-as-resource

Description

run-pex-as-resource now outputs pex_done, which can be used as a dependency for linking resources that depend on the pex script being run.

Related links

• #23

v0.1.5

Modules

• run-pex-as-resource

Description

run-pex-as-resource now supports configuring a destroy provisioner that runs the pex on destroy of the resource.

Related links

• #22