v0.17.0

fix: ensure the module does not instantiate an empty condition block @jhosteny (#43)

Guard the creation of the condition block on the length of the optional
listener_http_header_conditions.

Fixes #42

what

• Make the condition blocks dynamic, requiring a non-empty list for the http headers

why

• Without this, the module attempts to create an empty condition, and fails

references

Fixes #42

v0.16.1

Add load balacing algorithm type @sodre (#41)

what

• Expose the target group load_balancing_algorithm_type configuration as a variable.

why

• I would like to change from the default round_robin to least_outstanding_requests.

v0.16.0

Adding optional http_headers condition to listener @msmagoo87 (#40)

what

• Adding an optional http header condition to add to the ALB listener.

why

• The ability to add an http_header condition to a listener is desired in some cases. This will enable that ability.

v0.15.0

Update provider pinning, add context.tf, and add auto-release @joe-niland (#37)

what

• Relax version constraints for TF and providers
• Update module to use context.tf pattern
• Add auto-release Action

why

• Allow TF 0.13+, AWS provider 3+, etc
• Streamline common module variable usage
• Allow auto-release on merge to master

references

• None

0.14.0 add scope to oidc listener rule configuration

feat: add scope to oidc listener rule configuration (#35)

0.13.2

[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.13.1

[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.13.0: Update Version Pinning for Terraform to support 0.13 (#32)

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.
2. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

References

1. From PR #32

0.12.0: Migrate away from deprecated listener condition format

What

• Migrates the condition blocks away from the deprecated field/values variant in favor of the current block-syntax.

Why

• Recent versions of the aws provider do no longer work with lists for hosts/paths.

References

• #30

0.11.0: unauthenticated_priority and authenticated_priority are now optional (0 by default)

What

• All instances of priority will now default to unset unless var.authenticated_priority or var.unauthenticated_priority are given a value.

Why

• By setting it to null, the rule priority gets set automatically by amazon instead of defaulted by the module.