Skip to main content

Gruntwork release 2017-04

Guides / Update Guides / Releases / 2017-04

This page is lists all the updates to the Gruntwork Infrastructure as Code Library that were released in 2017-04. For instructions on how to use these updates in your code, check out the updating documentation.

Here are the repos that were updated:

terraform-aws-ci​

v0.3.12​

Published: 4/24/2017 | Release notes

  • The publish-ami script in the aws-helpers module now accepts an argument for --markdown-title-text so that the output markdown file may include an optional customized title.

v0.3.11​

Published: 4/23/2017 | Release notes

  • NEW MODULE: We've added a new module publish-ami that will copy the given AMI to the desired AWS regions (or all AWS regions) and make it public.

    We added this module because Gruntwork will soon be releasing open source modules for Vault, Nomad, and Consul and we needed a way to make AMIs built by those modules globally available and usable by anyone.

v0.3.10​

Published: 4/11/2017 | Release notes

  • UPDATE: build-go-binaries now defaults to CGO_ENABLED=0 to build completely static binaries that do not depend on a specific implementation of C. This was requested because an Alpine Linux user (using the musl C library) could not run one of our binaries. Note that a --cgo-enabled option has been added that defaults to false but can be set to true to revert to the original behavior.

v0.3.9​

Published: 4/6/2017 | Release notes

  • UPDATE: HashiCorp changed the GitHub Packer repo from github.com/mitchellh/packer to github.com/hashicorp/packer. Because our curl commands didn't handle a redirect, this caused some of our scripts to fail. This update fixes that issue.

terraform-aws-data-storage​

v0.2.5​

Published: 4/27/2017 | Release notes

POTENTIAL DOWNTIME

https://github.com/gruntwork-io/module-data-storage/pull/20: Fix a bug where the RDS and Aurora module would exit with an error if you set storage_encrypted to false.

Note: that if you update to this new version of module-data-storage and run apply, it will undeploy your old DB and deploy a new one to replace it. That's because fixing this bug required renaming the DB resources, which Terraform sees as a delete + create.

To avoid this, you will need to use the terraform state mv command.

Aurora

If you do not have encryption enabled:

terraform state mv module.database.aws_rds_cluster.cluster module.database.aws_rds_cluster.cluster_without_encryption

If you have encryption enabled:

terraform state mv module.database.aws_rds_cluster.cluster module.database.aws_rds_cluster.cluster_with_encryption

RDS

If you do not have encryption enabled:

terraform state mv module.database.aws_db_instance.primary module.database.aws_db_instance.primary_without_encryption
terraform state mv module.database.aws_db_instance.replicas module.database.aws_db_instance. replicas_without_encryption

If you have encryption enabled:

terraform state mv module.database.aws_db_instance.primary module.database.aws_db_instance.primary_with_encryption
terraform state mv module.database.aws_db_instance.replicas module.database.aws_db_instance. replicas_with_encryption

v0.2.4​

Published: 4/1/2017 | Release notes

https://github.com/gruntwork-io/module-data-storage/pull/18: The lambda snapshot functions now all expose the ID of the lambda IAM role via the output variable lambda_iam_role_id.

v0.2.3​

Published: 4/1/2017 | Release notes

https://github.com/gruntwork-io/module-data-storage/pull/17: Fix a bug in the lambda-copy-shared-rds-snapshot module where it didn't properly handle DBSnapshotNotFound errors.

v0.2.2​

Published: 4/1/2017 | Release notes

https://github.com/gruntwork-io/module-data-storage/pull/16: The copy-rds-shared-snapshot module now allows you to specify a KMS key via the optional kms_key_id parameter. If specified, this key will be used to encrypt the RDS snapshot copy.

terraform-aws-monitoring​

v0.4.3​

Published: 4/24/2017 | Release notes

terraform-aws-security​

v0.4.16​

Published: 4/28/2017 | Release notes

https://github.com/gruntwork-io/module-security/pull/31: Enable CGO to fix the ssh-iam build so that the user.Current() method works. Only build ssh-iam for Linux.

v0.4.15​

Published: 4/27/2017 | Release notes

https://github.com/gruntwork-io/module-security/pull/30: Build the ssh-iam binary with Go 1.8.1.

v0.4.14​

Published: 4/27/2017 | Release notes

  • NEW MODULE: We've added a module, iam-user-password-policy that makes it easy to use Terragrunt to create a password policy for your IAM Users.

v0.4.13​

Published: 4/26/2017 | Release notes

https://github.com/gruntwork-io/module-security/pull/27: Try to fix the ssh-iam build by upgrading to Go 1.8.

v0.4.12​

Published: 4/26/2017 | Release notes

https://github.com/gruntwork-io/module-security/pull/26: Ensure that ssh-iam always exits successfully when called from the AuthorizedKeysCommand, logs everything to stderr, and sends stderr to syslog.

v0.4.11​

Published: 4/25/2017 | Release notes

https://github.com/gruntwork-io/module-security/pull/24: Fix a bug in the auto-update module that would cause it to show an interactive prompt during install. This could cause automated builds to hang forever.

v0.4.10​

Published: 4/2/2017 | Release notes

https://github.com/gruntwork-io/module-security/pull/23: Add support for cross-account CloudTrail.

v0.4.9​

Published: 4/1/2017 | Release notes

https://github.com/gruntwork-io/module-security/pull/22: In the kms-master-key module, KMS key users now get the CreateGrant permission. This makes it possible to share RDS snapshots encrypted with this KMS key with another AWS account.

terraform-aws-static-assets​

v0.0.1​

Published: 4/4/2017 | Release notes

First release!