Skip to main content

Gruntwork release 2018-02

Guides / Update Guides / Releases / 2018-02

This page is lists all the updates to the Gruntwork Infrastructure as Code Library that were released in 2018-02. 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-cache​

v0.3.3​

Published: 2/27/2018 | Release notes

https://github.com/gruntwork-io/module-cache/pull/17: You can now enable encryption at rest and in transit for Redis using the new parameters enable_at_rest_encryption and enable_transit_encryption. Note that if you already have Redis deployed without encryption, you cannot enable encryption for it; you must create a new Redis cluster that has encryption enabled and migrate to that.

terraform-aws-ci​

v0.7.1​

Published: 2/22/2018 | Release notes

https://github.com/gruntwork-io/module-ci/pull/53: The install-jenkins module now supports CentOS.

v0.7.0​

Published: 2/20/2018 | Release notes

https://github.com/gruntwork-io/module-ci/pull/52:

Warning: this release contains BACKWARDS INCOMPATIBLE CHANGES to scheduled-lambda-job.

  • Add new modules for running Jenkins: jenkins-server and install-jenkins.
  • Add a module for running a Lambda function on a scheduled basis to take snapshots of your servers: ec2-backup.
  • Delete the scheduled-lambda-job module. Please migrate to package-lambda instead. You can create the Lambda functions with the lambda module and run them on a scheduled basis using the scheduled-lambda-job module in that repo.
  • Update this repo to use CircleCI 2.0 with the machine executor.
  • Add a new --circle-ci-2-machine-executor flag to configure-environment-for-gruntwork-module so you can use the script with CircleCI 2.0's machine executor.
  • Add an example for how to create "unit tests" for modules that run locally and relatively quickly using Docker and Docker Compose. See jenkins_test.go.
  • Add an example for how to create "integration tests" out of multiple "stages," where any one of the stages can be skipped to speed up local iterative development. See jenkins_test.go.

terraform-aws-ecs​

v0.6.2​

Published: 2/20/2018 | Release notes

https://github.com/gruntwork-io/module-ecs/pull/54: You can now configure a health check grace period for your ECS services using the new health_check_grace_period_seconds parameter! Also, we've added another depends_on clause for the ALB Target Group in the ecs-service-with-alb module, which should help work around https://github.com/hashicorp/terraform/issues/12634.

terraform-aws-messaging​

v0.1.0​

Published: 2/6/2018 | Release notes

terraform-aws-openvpn​

v0.5.3​

Published: 2/27/2018 | Release notes

terraform-aws-sam​

v0.0.3​

Published: 2/14/2018 | Release notes

remove the terraform block from the generated terraform module

terraform-aws-security​

v0.7.1​

Published: 2/22/2018 | Release notes

https://github.com/gruntwork-io/module-security/pull/73: Use a more reliable way to look up the path to the ssh-iam binary during the install process.

terraform-aws-server​

v0.4.1​

Published: 2/23/2018 | Release notes

v0.4.0​

Published: 2/22/2018 | Release notes

https://github.com/gruntwork-io/module-server/pull/26:

Note, this release contains BACKWARDS INCOMPATIBLE CHANGES to the single-server module. Read on for more info

  1. The persistent-ebs-volume module now supports CentOS.

  2. Fixed a number of minor bugs in the persistent-ebs-volume module. All AWS API calls in mount-ebs-volume are now done with retries, as there are transient reasons why they might fail (e.g., IAM permissions taking a while to propagate). Fix a syntax error in unmount-ebs-volume.

  3. The aws_security_group in now uses name_prefix instead of name and sets create_before_destroy to true. This should fix the DependencyViolation: resource sg-XXX has a dependent object error described in https://github.com/terraform-providers/terraform-provider-aws/issues/1671. However, this will result in the Security Group being renamed and therefore, recreated. To update to this new version of single-server, which is used in the bastion host, OpenVPN server, Jenkins, and elsewhere, you'll need to:

    1. Find all resources that depend on this security group and remove that dependency. It is OK to do this in the AWS UI.
    2. Run apply with this new single-server version to create the new security group.
    3. Run apply in each module from step 1 to recreate the dependency.