Skip to main content

Gruntwork release 2018-09

Guides / Update Guides / Releases / 2018-09

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

v0.6.17​

Published: 9/27/2018 | Release notes

v0.6.16​

Published: 9/26/2018 | Release notes

terraform-aws-ci​

v0.13.2​

Published: 9/18/2018 | Release notes

terraform-aws-data-storage​

v0.6.8​

Published: 9/20/2018 | Release notes

terraform-aws-ecs​

v0.8.5​

Published: 9/30/2018 | Release notes

https://github.com/gruntwork-io/module-ecs/pull/92: You can now configure volumes for the ecs-service module using the new volumes parameter.

v0.8.4​

Published: 9/20/2018 | Release notes

https://github.com/gruntwork-io/module-ecs/pull/91: The ecs-service-with-discovery module now outputs the security group ID via the output variable ecs_task_security_group_id.

terraform-aws-elk​

v0.2.5​

Published: 9/27/2018 | Release notes

Also added proper plumbing for allow_ssh_from_security_group_ids to be specified in the elastalert module and then be passed all the way through to the underlying elastalert-security-group-rules module

v0.2.4​

Published: 9/25/2018 | Release notes

v0.2.3​

Published: 9/25/2018 | Release notes

v0.2.2​

Published: 9/24/2018 | Release notes

Resolved #46 with PR #49. We were missing an equals sign. There was some inconsistent behavior with some customers reporting issues as a result while other tests running and passing without issue.

v0.2.1​

Published: 9/24/2018 | Release notes

Resolved issue: #47 with PR: #48.

All other cluster outputs (elastalert, elasticsearch, kibana) have an iam_role_id output but logstash-cluster was missing this variable:

output "iam_role_id" {
  value = "${module.logstash_cluster.iam_role_id}"
}

This variable is useful for adding ssh-grunt IAM policies to this ASG. Thank you to @Merlz for pointing out the oversight.

v0.2.0​

Published: 9/19/2018 | Release notes

This release includes some major changes:

  1. Adds support for alerting on patterns with Elastalert
  2. Replaces the usage of an NLB with an ALB instead
  3. Adds an auto discovery script to the Filebeat deployment to bypass the need for a load balancer between the application server and Logstash cluster.

Here's why we removed the NLB:

This release is backwards incompatible with previous releases. To upgrade you need to follow the following steps:

  1. Remove your use of the nlb module and replace with an alb. See example here: https://github.com/gruntwork-io/package-elk/blob/master/examples/elk-multi-cluster/main.tf#L436
  2. Replace your use of the load-balancer-target-group module with load-balancer-alb-target-group. See example of using the new module https://github.com/gruntwork-io/package-elk/blob/master/examples/elk-multi-cluster/main.tf#L71
  3. Finally update the various target_group_arns arguments passed to the cluster modules. https://github.com/gruntwork-io/package-elk/blob/master/examples/elk-multi-cluster/main.tf#L40
  4. If you're using SSL with the ALB, you'll need to take note of the upgrade notes here: https://github.com/gruntwork-io/module-load-balancer/releases/tag/v0.12.0

v0.1.1​

Published: 9/4/2018 | Release notes

Going forward, the ALB will be our "front facing" load balancer that will be how users access apps like Kibana. The ultimate goal will be to remove the NLB entirely rather than having to run both kinds of load balancers. We should be able to achieve this goal with #43

terraform-aws-lambda​

v0.2.3​

Published: 9/24/2018 | Release notes

https://github.com/gruntwork-io/package-lambda/pull/21: Add a new parameter called wait_for to the lambda module. All the resources in the module will not be created until wait_for is resolved, which allows you to execute other steps (e.g., create zip file) before this module runs. This is a workaround for the lack of depends_on for modules in Terraform.

terraform-aws-load-balancer​

v0.12.0​

Published: 9/18/2018 | Release notes

  • https_listener_ports_and_acm_ssl_certs_num to specify the length of https_listener_ports_and_acm_ssl_certs
  • https_listener_ports_and_ssl_certs_num to specify the length of https_listener_ports_and_ssl_certs

This helps bypass the Terraform bug where the contents of those variables depend on dynamic resources hashicorp/terraform#11482.

This release is BACKWARD INCOMPATIBLE with previous releases only if you were using SSL certs. To upgrade you'll need to specify the newly added variables and run terraform apply.

v0.11.1​

Published: 9/7/2018 | Release notes

terraform-aws-messaging​

v0.1.1​

Published: 9/6/2018 | Release notes

terraform-aws-sam​

v0.1.7​

Published: 9/27/2018 | Release notes

This release introduces the ability to pass environment variables along to lambdas while testing locally using AWS SAM CLI

v0.1.6​

Published: 9/25/2018 | Release notes