v0.22.0

Add health_check_path to allow the health check to use a port other than traffic-port @msmagoo87 (#63)

what

• Allows the specification of a health check port that is not the traffic-port.

why

• The health check endpoint doesn't necessarily always exist on the default traffic-port, as is my case.

v0.21.0

fix: update s3 bucket & context tags @tirumerla (#62)

what

• Bump the tag for s3 bucket module to use >= 2.0 for aws provider to avoid module version conflicts when used with >= 3.0 modules (eg. aws-eks-node-group).
• Bump the tag to 0.21.0 for terraform-null-label module to support future versions of TF.

why

• This module is being used with terraform-aws-eks-node-group which needs aws provider version to be >= 2.0 to fix version conflicts.

references

• See cloudposse/terraform-aws-eks-node-group#41 for details. This tackles one of the modules causing the issue.

v0.20.0

update to context @syphernl (#60)

what

• Update to context.tf.

why

• In v0.19.0 the enabled var was added manually instead of via context.

references

• Refs #56

v0.19.0

Add enabled variable @jblackburn22 (#56)

what

This allows the ALB to be created selectively.

why

As a cost saving measure, I want to be able to create an ALB per AWS account for a given application and then create multiple target groups.

references

• This addresses #55.

v0.18.0

Updated version constraints @MartinCanovas (#59)

The aws = ~> 2.0 causes error in Terraform 0.13:

Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider hashicorp/aws:
no available releases match the given constraints >= 3.0.*, >= 2.0.*, >=
2.0.*, >= 2.0.*, >= 2.0.*, >= 2.0.*, < 4.0.*, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0,
~> 2.0, ~> 2.0, >= 2.0.*, < 4.0.*, >= 3.0.*, >= 2.0.*, >= 2.0.*, >= 2.0.*

what

• Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
• Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a GitHub issue #123

v0.17.0

fix: update upsteam dependency @OblateSpheroid (#54)

what

• module access_logs is using tagged version that has issues with TF 0.13, so updating to use a fixed version of that module

why

• this module currently fails with TF 0.13, and has no tests for TF 0.13 to automatically detect these issues

v0.16.0

bump aws-lb-s3-bucket version @shakhanton (#50)

what

• change version of terraform-aws-lb-s3-bucket module

why

• version 0.4.0 doesn't work with terraform 0.13.0

v0.15.0

[AUTOMATED] Update terraform-null-label versions to support Terraform 0.13 @Gowiem (#51)

What

1. Updates terraform-null-label versions 0.14.1, 0.15.0, and 0.16.0 to version 0.17.0
2. This is an automated commit and pull request created by Microplane. More information here.

Why

1. This module and the mentioned previous versions are used extensively across the large majority of Cloud Posse's Terraform Modules. They're currently holding back support for Terraform v0.13. Doing this upgrade in mass will alleviate the pain in our efforts to support Terraform v0.13

v0.14.0

Update to go modules @osterman (#53)

what

• Update to go modules
• Test new slash dispatch command
• Revert rolback of auto-release config

why

• Upgraded slash command and need to verify it's working
• Use go modules for easier invocation

v0.13.2

• update chatops @osterman (#52)