Gruntwork release 2018-05
Guides / Update Guides / Releases / 2018-05
This page is lists all the updates to the Gruntwork Infrastructure as Code
Library that were released in 2018-05. For instructions
on how to use these updates in your code, check out the updating
documentation.
Here are the repos that were updated:
Published: 5/16/2018 | Release notes
Published: 5/9/2018 | Release notes
Published: 5/31/2018 | Release notes
Published: 5/9/2018 | Release notes
The following changes were made to the server-group module:
- IMPROVEMENT: Fixed an issue where an Auto Scaling Group's
DesiredInstances property was left at 0 after the rolling_deployment.py script failed to reach a passing health check before timing out. (#29) - IMPROVEMENT: Expose
var.deployment_health_check_max_retries and var.deployment_health_check_retry_interval_in_seconds so that Terraform code that calls the server-group module can control how long the rolling_deployment.py will run before timing out. (#29) - IMPROVEMENT: Updated to latest version of Boto to address transient AWS issues. (#29)
- IMPROVEMENT: Expose
var.additional_security_group_ids to add arbitrary Security Groups to the Launch Configuration created.
Published: 5/25/2018 | Release notes
https://github.com/gruntwork-io/module-ci/pull/60: The git-add-commit-push script no longer defaults the branch name to $CIRCLE_BRANCH. Instead, it uses git to look up the name of the currently checked-out branch in pwd. In most cases this will produce the exact same effect as before and no code changes will be required. Note that you can always use the --branch-name argument to override the default branch name in git-add-commit-push.
Published: 5/24/2018 | Release notes
https://github.com/gruntwork-io/module-ci/pull/58:
BACKWARDS INCOMPATIBLE CHANGES
git-add-commit-push has been moved from the gruntwork-module-circleci-helpers module to the git-helpers module.terraform-update-variable now depends on git-helpers being installed, as it uses git-add-commit-push under the hood to be able to more reliably commit and push changes.
Published: 5/16/2018 | Release notes
Published: 5/21/2018 | Release notes
Published: 5/17/2018 | Release notes
https://github.com/gruntwork-io/module-data-storage/pull/47: In the aurora module, you can now use the db_instance_parameter_group_name param to set the parameter group for instances separately from the parameter group for the entire cluster (which can be set via the db_cluster_parameter_group_name param).
Published: 5/4/2018 | Release notes
Published: 5/2/2018 | Release notes
Published: 5/14/2018 | Release notes
Published: 5/8/2018 | Release notes
Published: 5/27/2018 | Release notes
Published: 5/24/2018 | Release notes
terragrunt state mv module.<module>.aws_lb.nlb module.<module>.aws_lb.nlb_<num>_az
Replace <module> with the name of your module and <num> with the amount of subnet mappings you provided. See an example for more details.
Published: 5/8/2018 | Release notes
Published: 5/8/2018 | Release notes
Published: 5/7/2018 | Release notes
- fix a bug where all HTTP verbs were not being handled properly
- fix a bug where multiple HTTP verbs defined on the same endpoint were not being processed sucessfully
Published: 5/30/2018 | Release notes
https://github.com/gruntwork-io/module-security/pull/93:
BACKWARDS INCOMPATIBLE CHANGE
The cross-account-iam-roles module now sets a default max expiration of 12 hours for IAM Roles intended for human users (e.g., allow-read-only-access-from-other-accounts) and a default max expiration of 1 hour for IAM Roles intended for machine users (e.g., allow-auto-deploy-access-from-other-accounts). Both of these expiration values are configurable via the new input variables max_session_duration_human_users and max_session_duration_machine_users.
The aws-auth script now accepts optional --mfa-duration-seconds and --role-duration-seconds parameters that specify the session expiration for the creds you get back when authenticating with an MFA token or assuming an IAM role, respectively. The default for both of these has been set to 12 hours to be more human-friendly.
Published: 5/28/2018 | Release notes
https://github.com/gruntwork-io/module-security/pull/92:
BACKWARDS INCOMPATIBLE CHANGES
The auto-update, ntp, fail2ban, and ip-lockdown modules now all use bash-commons under the hood. That means you must install bash-commons before installing any of those other modules.
The auto-update and ntp modules now support Amazon Linux 2. We will add Amazon Linux 2 support for fail2ban and ip-lockdown modules in the future.