Releases: cloudposse/terraform-aws-alb
v1.8.0
v1.7.0
Add load_balancing_algorithm_type input variable @linhkikuchi (#127)
what
- To support other type of load_balancing_algorithm_type (other than the default
round_robin
)
why
- My use case requires to use
least_outstanding_requests
type
v1.6.0
add preserve host header option @tbpoetke (#124)
what
adding the preserve host header option of the alb like documented here: Terraform registry
why
option was missing
references
- closes #123
v1.5.0
v1.4.0
chore(deps): update Terraform cloudposse/lb-s3-bucket/aws to v0.16.0 @renovate (#111)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/lb-s3-bucket/aws (source) | module | minor | 0.14.1 -> 0.16.0 |
v1.3.0
Add attribute protocol_version into default target group @ArtemKorchunov (#118)
what
- Add attribute
protocol_version
to default target group
why
- This attribute is mentioned in docs for lb_target_group https://registry.terraform.io/providers/hashicorp/aws/3.61.0/docs/resources/lb_target_group#protocol_version
v1.2.0
feat: add variable to support health check protocol different from traffic's @topikachu (#117)
what
Add variable to support health check protocol different from traffic's
why
My system uses HTTP for the health check but HTTPS for data traffic.
Add a new variable to support this use case.
references
v1.1.0
v1.0.0
Initial release with production Semantic Versioning, part of our general strategy to convert to production versioning as we make updates to relatively mature modules, especially those where we see breaking changes coming in the near future. This module will evolve with breaking changes as we convert it to use our security-group
and s3-log-storage
modules and be compatible with the new S3 resource structure introduced in AWS Terraform provider v4.0.
v0.36.0
Fix default target group count @linhkikuchi (#108)
what
- I have
listener_https_fixed_response
but still need the default target group created in this module. It used to work before this PR (#97). Do not see why it should not get created when we havelistener_https_fixed_response