Skip to main content

Gruntwork release 2016-06

Guides / Update Guides / Releases / 2016-06

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

Here are the repos that were updated:

gruntkms

v0.0.3

Published: 6/29/2016 | Release notes

  • Fix a bug where the decrypt command did not properly report AWS error messages and would fail silently.

v0.0.2

Published: 6/29/2016 | Release notes

  • Statically link the gruntkms binaries

v0.0.1

Published: 6/20/2016 | Release notes

  • First release

terraform-aws-ci

v0.0.10

Published: 6/20/2016 | Release notes

  • Fix a bug in upload-github-release-assets where the default values for repo name and owner name, read from Circle CI env vars, were backwards.

v0.0.9

Published: 6/20/2016 | Release notes

  • Add more logging and error checking to upload-github-release-assets

v0.0.8

Published: 6/20/2016 | Release notes

  • Use GitHub release tag API to retrieve id of the release in upload-github-release-assets

v0.0.7

Published: 6/20/2016 | Release notes

  • Fix flag parsing in build-go-binaries: it now correctly looks for --ld-flags instead of --ld_flags.

v0.0.6

Published: 6/13/2016 | Release notes

  • Fix a bug in the git-add-commit-push. It now does git config before add or commit.

v0.0.5

Published: 6/13/2016 | Release notes

Add 3 new helpers to the gruntwork-module-circleci-helpers module:

  • build-go-binaries: automatically build binaries for Go apps.
  • git-add-commit-push: automatically add, commit, and push changes to Git.
  • upload-github-release-assets: automatically upload assets to a GitHub release.

v0.0.4

Published: 6/12/2016 | Release notes

  • Fix a bug in run-go-tests with glide novendor and newlines.

v0.0.3

Published: 6/12/2016 | Release notes

  • The --path parameter in run-go-tests is now optional and defaults to the current working directory.

v0.0.2

Published: 6/12/2016 | Release notes

  • Add a new --packages parameter to run-go-tests that allows you to specify which packages to test separate from the --path parameter, which is now just for setting the working directory. The default --packages value is the output of running glide novendor in --path.

v0.0.0

Published: 6/12/2016 | Release notes

This release is used solely for automated testing of the upload-github-release-assets script. Do not use this for anything in production!

v0.0.1

Published: 6/7/2016 | Release notes

  • First release in this standalone repo!

terraform-aws-data-storage

v0.0.4

Published: 6/22/2016 | Release notes

  • All data stores now support a bastion_host_security_group_id parameter that can be used to allow the bastion host (or more likely, you using the bastion host via SSH tunneling) to connect to the data store. For security reasons, the default for the bastion_host_security_group_id parameter is empty string, which means it's disabled.

v0.0.3

Published: 6/16/2016 | Release notes

redis module now treats auto-failover as optional. This is useful if you wish to launch a stage redis but reduce cost by launching just a single node.

v0.0.2

Published: 6/14/2016 | Release notes

  • redismodule now accepts a bastion_host_security_group_id so it can accept connections specifically from the Bastion Host, not just a CIDR range.

v0.0.1

Published: 6/10/2016 | Release notes

Initial release!

terraform-aws-ecs

v0.0.6

Published: 7/1/2016 | Release notes

  • For ecs-cluster and ecs-server modules, terraform output values containing a value like iam_role_name now output a human-friendly name, not a globally unique string ID as before.
  • Due to Terraform Bug #3888, a bug was introduced in an earlier release when using the ecs-cluster module from a terraform template that is in turn called by another terraform template. This release fixes that bug by adding an explicit var allow_ssh to indicate whether SSH from a specific security group will be allowed. This is redundant but resolves the issue until the Terraform bug is resolved.

v0.0.5

Published: 6/30/2016 | Release notes

  • Module ecs-cluster now outputs the more standardized names of ecs_instance_iam_role_arn and ecs_instance_iam_role_name.

v0.0.4

Published: 6/29/2016 | Release notes

  • Module ecs-service now outputs the ECS Service ARN value
  • Minor bug fixes around how the ECR region is handled

v0.0.3

Published: 6/22/2016 | Release notes

  • Fix bug where the ecs-service module did not work properly if you did not associate it with an ELB

v0.0.2

Published: 6/21/2016 | Release notes

  • The allow_ssh_from_security_group_id variable on the ecs-cluster module is now required. The module also now handles an empty string value correctly for that variable, so you can set it to an empty string to disallow SSH connections.
  • Added a discussion of how to handle updates to ECS cluster instances to the ecs-cluster README.

v0.0.1

Published: 6/8/2016 | Release notes

First release in this repo!

terraform-aws-monitoring

v0.0.6

Published: 6/30/2016 | Release notes

  • The run-cloudwatch-logs-agent.sh now supports 3 parameters: --vpc-name, --log-group-name, and --log-stream-name.

v0.0.5

Published: 6/28/2016 | Release notes

  • The route53-health-check module now enforces that the CloudWatch Alarm and SNS Topic for the Route 53 Health Check are both in us-east-1, as that's the only place where Route 53 sends CloudWatch metrics.

v0.0.4

Published: 6/27/2016 | Release notes

  • Don't trigger alarms when ELB request latency switches to INSUFFICIENT_DATA state, as that indicates no requests are going through the ELB, which might not be an error condition, and if it is, should be caught by the elb_low_request_count alarm instead.
  • Only create the elb_low_request_count alarm if var.elb_low_request_count_threshold is greater than 0.

v0.0.3

Published: 6/27/2016 | Release notes

  • All alarm names are now parameterized using the relevant resource name (e.g. ELB alarms include the ELB name in their own name) so that you do not have name conflicts if you use the same alarm more than once.
  • Added alarms for RDS. See modules/alarms/rds-alarms.
  • Added alarms for ECS. See modules/alarms/ecs-cluster-alarms and modules/alarms/ecs-service-alarms.

v0.0.2

Published: 6/24/2016 | Release notes

  • The install-cloudwatch-logs-agent.sh script now properly configures the AWS region on Amazon Linux too

v0.0.1

Published: 6/17/2016 | Release notes

  • First release in this repo!

terraform-aws-server

v0.0.2

Published: 6/7/2016 | Release notes

  • Rename standalone-server module to single-server

v0.0.1

Published: 6/7/2016 | Release notes

  • First release in this new standalone repo!

terraform-aws-vpc

v0.0.4

Published: 6/24/2016 | Release notes

  • Fix bug where VPC templates defined a route both inline to aws_route_table terraform resource and externally as an aws_route. Now all routes are defined as an aws_route, so that Terraform will behave correctly.

v0.0.3

Published: 6/17/2016 | Release notes

  • Fix bug where private subnets could not make calls to the public Internet.
  • Remove the nat_gateway_ips and num_nat_gateway_ips parameters from the network-acl modules.

v0.0.2

Published: 6/10/2016 | Release notes

  • Add modules for configuring Network ACLs to control network communication between subnets: vpc-app-network-acls, vpc-mgmt-network-acls, network-acl-outbound, network-acl-inbound.

v0.0.1

Published: 6/8/2016 | Release notes

First release in this repo!