This repo contains miscellaneous utility and helper modules for use with Terraform.

This repo provides a Gruntwork IaC Package and has the following folder structure:

• modules: This folder contains the main implementation code for this repository, broken down into multiple standalone modules.
• examples: This folder contains examples of how to use the modules.
• test: Automated tests for the modules and examples.

The following modules are available:

• join-path: This module can be used to join a list of given path parts into a single path that is platform/operating system aware. (This module requires Python)
• operating-system: This module can be used to figure out what operating system is being used to run Terraform. (This module requires Python)
• require-executable: This is a module that can be used to ensure particular executables is available in the PATH. (This module requires Python)
• run-pex-as-data-source: This module prepares a portable environment for running PEX files and runs them as an external data source. PEX files are python executables that contain all the requirements necessary to run the script. (This module requires Python)
• run-pex-as-resource: This module prepares a portable environment for running PEX files and runs them as an local-exec provisioner on a null_resource. PEX files are python executables that contain all the requirements necessary to run the script. (This module requires Python)

The following modules were deprecated and removed:

• intermediate-variable: This module has been superseded by terraform local values. To upgrade, switch usage of intermediate-variable with locals.

• enabled-aws-regions: This module has been superseded by terraform aws_regions data source. To upgrade, switch the module block with:

  data "aws_regions" "enabled_regions" {}

  Then, you can get the list of enabled regions using data.aws_regions.enabled_regions.names.

Click on each module above to see its documentation. Head over to the examples folder for example usage.

A Module is a canonical, reusable, best-practices definition for how to run a single piece of infrastructure, such as a database or server cluster. Each Module is written using a combination of Terraform and scripts (mostly bash) and include automated tests, documentation, and examples. It is maintained both by the open source community and companies that provide commercial support.

Instead of figuring out the details of how to run a piece of infrastructure from scratch, you can reuse existing code that has been proven in production. And instead of maintaining all that infrastructure code yourself, you can leverage the work of the Module community to pick up infrastructure improvements through a version number bump.

This Module is maintained by Gruntwork. If you're looking for help or commercial support, send an email to [email protected]. Gruntwork can help with:

• Setup, customization, and support for this Module.
• Modules for other types of infrastructure, such as VPCs, Docker clusters, databases, and continuous integration.
• Modules that meet compliance requirements, such as HIPAA.
• Consulting & Training on AWS, Terraform, and DevOps.

This Module follows the principles of Semantic Versioning. You can find each new release, along with the changelog, in the Releases Page.

During initial development, the major version will be 0 (e.g., 0.x.y), which indicates the code does not yet have a stable API. Once we hit 1.0.0, we will make every effort to maintain a backwards compatible API and use the MAJOR, MINOR, and PATCH versions on each release to indicate any incompatibilities.

Please see LICENSE.txt and NOTICE for details on how the code in this repo is licensed.