Skip to content

Releases: cloudposse/terraform-aws-alb

v0.20.0

10 Nov 11:13
55ef256
Compare
Choose a tag to compare
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

v0.19.0

18 Oct 19:34
c3c8dd8
Compare
Choose a tag to compare
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

21 Sep 14:58
33ce732
Compare
Choose a tag to compare
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

19 Aug 03:01
43510ae
Compare
Choose a tag to compare
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

18 Aug 08:34
4d10c2e
Compare
Choose a tag to compare
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

18 Aug 06:45
3e6687d
Compare
Choose a tag to compare
[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

18 Aug 06:42
6f9aaeb
Compare
Choose a tag to compare
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

18 Aug 05:47
344b41f
Compare
Choose a tag to compare

0.13.1

14 Aug 07:16
d710c7a
Compare
Choose a tag to compare
[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.13.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#47)

12 Aug 01:38
b6957ff
Compare
Choose a tag to compare
## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.