Skip to main content

Gruntwork release 2016-07

Guides / Update Guides / Releases / 2016-07

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

Here are the repos that were updated:

boilerplate

v0.0.2

Published: 7/1/2016 | Release notes

  • A few fixes for the README

v0.0.1

Published: 7/1/2016 | Release notes

First release!

terraform-aws-asg

v0.0.3

Published: 7/26/2016 | Release notes

  • Add Gruntwork license

v0.0.2

Published: 7/24/2016 | Release notes

  • Publish public documentation to module-asg-public after each release

v0.0.1

Published: 7/12/2016 | Release notes

First release in this repo!

terraform-aws-cache

v0.0.1

Published: 7/30/2016 | Release notes

  • First release in this repo!

terraform-aws-ci

v0.0.17

Published: 7/26/2016 | Release notes

  • Add Gruntwork license

v0.0.16

Published: 7/24/2016 | Release notes

  • The build for this repo now generates docs from a clean checkout to ensure that none of the output from the earlier parts of the Circle CI build (e.g. compiled binaries, local test files, etc) are included in the generated docs.

v0.0.15

Published: 7/24/2016 | Release notes

  • Output docs-generator binaries to a different folder during the build so they don't get pushed to the module-ci-public repo

v0.0.14

Published: 7/22/2016 | Release notes

  • Add a new docs-generator module that can generate public documentation for a private GitHub repo

v0.0.13

Published: 7/12/2016 | Release notes

  • Add new build-helpers module with build-docker-image and build-packer-artifact scripts.
  • Add new terraform-helpers module with terraform-deploy and terraform-update-variable scripts.

v0.0.12

Published: 7/12/2016 | Release notes

  • Fix bug in configure-environment-for-gruntwork-module where it would not handle multiple --go-src-path parameters correctly.

v0.0.11

Published: 7/1/2016 | Release notes

Several fixes to the git-add-commit-push script:

  • When checking if there is something to commit, also check if this is a new, unstated path.
  • Make the exit code for “nothing to commit” configurable using the --no-commit-exit-code flag. The default is 0.

terraform-aws-data-storage

v0.0.7

Published: 7/29/2016 | Release notes

  • Migrate elasticache code to module-cache

v0.0.6

Published: 7/26/2016 | Release notes

  • Add Gruntwork license

v0.0.5

Published: 7/24/2016 | Release notes

  • Publish public documentation to module-data-storage-public after each release

terraform-aws-ecs

v0.1.6

Published: 7/26/2016 | Release notes

  • Add Gruntwork license

v0.1.5

Published: 7/24/2016 | Release notes

  • Publish public documentation to module-ecs-public after each release

v0.1.4

Published: 7/14/2016 | Release notes

  • BREAKING CHANGE: ecs-service params are renamed to more cleanly separate ELB resources from non-ELB resources by namespacing vars as either elb_ or not.
  • Rolls back #16 since this can be put in clients' infrastructure-modules repo instead.

v0.1.3

Published: 7/14/2016 | Release notes

  • ecs-cluster: The ECS Node IAM Role now has limited permissions to discover information about its environment. This is useful when bootstrapping a distributed cluster in ECS.

v0.1.2

Published: 7/14/2016 | Release notes

  • Bug Fix: ecs-service: Previously, this module created an IAM Role for the ECS Service only when an ELB was in use. When we tried to create an ECS Service without an ELB, this was exposed as a bug and is now fixed.

v0.1.1

Published: 7/13/2016 | Release notes

  • Bug Fix: configure-ecs-instance script claimed to append to the existing crontab but actually overwrote it. Now fixed!

v0.1.0

Published: 7/4/2016 | Release notes

  • ecs-service: BREAKING CHANGE. The name property has been renamed to service_name.
  • ecs-service: BREAKING CHANGE. The associate_with_elb property has been renamed to is_associated_with_elb to better indicate this property accepts boolean values.
  • ecs-service: BREAKING CHANGE. The ecs_cluster_vpc_name property has been added so that the ECS Service's IAM Role is named uniquely per the environment in which it's deployed.
  • Tests updated to use latest gruntwork-installer.

v0.0.7

Published: 7/3/2016 | Release notes

  • ecs-cluster and ecs-servce now output ecs_cluster_arn instead of ecs_cluster_id. This was done to improve clarity about what this var represents.

terraform-aws-monitoring

v0.0.8

Published: 7/26/2016 | Release notes

  • Add Gruntwork license

v0.0.7

Published: 7/24/2016 | Release notes

  • Generate public documentation into module-aws-monitoring-public on each release

terraform-aws-security

v0.0.1

Published: 7/26/2016 | Release notes

  • First release!

terraform-aws-server

v0.0.5

Published: 7/26/2016 | Release notes

  • Add Gruntwork license

v0.0.4

Published: 7/24/2016 | Release notes

  • Generate public documentation for this repo on each release

v0.0.3

Published: 7/12/2016 | Release notes

Add two new modules:

  • persistent-ebs-volume: Scripts for mounting and unmounting EBS Volumes on your EC2 Instances for Volumes that need to persist between redeploys of the Instance.
  • route53-helpers: Scripts for working with Amazon's DNS Service, Route 53, including a script to add a DNS A record pointing to the instance's IP address.

terraform-aws-vpc

v0.0.8

Published: 7/26/2016 | Release notes

  • Add Gruntwork license

v0.0.7

Published: 7/24/2016 | Release notes

  • Publish public documentation to module-vpc-public for each release

v0.0.6

Published: 7/8/2016 | Release notes

  • Add a new vpc-peering-external module for setting up Routes and Network ACLs for VPC Peering Connections with 3rd parties.

v0.0.5

Published: 7/7/2016 | Release notes

  • Fix a bug in the Network ACLs where they would only allow connections between subnets of the same type (e.g. two private app subnets) on ports >= 1024. Now all ports should work.
  • Remove extraneous outbound Network ACLs in the private app subnets, since the Network ACLs for those subnets allow all outbound access.
  • The VPC modules now have a new output called vpc_ready and the Network ACL modules now require a new input called vpc_ready. You should feed the former into the latter. This is used to work around a Terraform or AWS timing bug related to creating ACLs at the same time as the VPC and its gateways. See https://github.com/hashicorp/terraform/issues/7527 for details.