v0.29.2

🤖 Automatic Updates

Update context.tf @cloudpossebot (#76)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.29.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#72)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.29.0

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#73)

what

• update context.tf to v0.23.0
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.28.2

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#74)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.28.1

🤖 Automatic Updates

chore(deps): update terraform cloudposse/lb-s3-bucket/aws to v0.10.1 @renovate (#71)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/lb-s3-bucket/aws (source)	terraform	patch	0.10.0 -> 0.10.1

---

Release Notes

cloudposse/terraform-aws-lb-s3-bucket

v0.10.1

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/s3-log-storage/aws to v0.18.0 @​renovate (#​30)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-log-storage/aws (source)	terraform	minor	0.17.0 -> 0.18.0

---

Release Notes

cloudposse/terraform-aws-s3-log-storage

##### [`v0.18.0`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/0.18.0)

Compare Source

Bc compliance @​&#​8203;maximmi (#&#​8203;49)

##### what * BridgeCrew compliance checks fix * readme updated * default behaviour changed: `S3 bucket MFA delete` enabled by default * default behaviour changed: `S3 Bucket Versioning` enabled by default * default behaviour changed: `Encryption of the S3 bucket` enabled by default ##### why * To be able to position our modules as standards compliant * stay in sync with code * To comply BridgeCrew check ##### references * https://docs.bridgecrew.io/docs/s3_16-enable-versioning * https://docs.bridgecrew.io/docs/s3_13-enable-logging * https://docs.bridgecrew.io/docs/s3_14-data-encrypted-at-rest

v0.28.0

🚀 Enhancements

Enable or disable the default security group @nitrocode (#70)

what

• Allows enabling or disabling the security group

why

• If we don't need another security group, why create it?

references

N/A

v0.27.0

Terraform 0.14 upgrade @maximmi (#68)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.26.0

Add fixed response option on listeners (http or https) @msmagoo87 (#69)

what

• Add an optional fixed response to the default auction of the listener (http or https).

why

• I have a case where I am using a Cloudfront distribution that passes a special header to verify the validity of the request (as described here https://www.arhs-group.com/protecting-aws-alb-behind-aws-cloudfront-distribution/). I want to use a listener rule to respond with a 403 if that header is missing or incorrect. Since the module always forwards to the TG unconditionally, I am adding this feature as an alternative.

v0.25.0

Add 0.14 support and update new syntax @snowsky (#67)

what

• Add Terraform 0.14 support
• Use new syntax in main.tf/versions.tf

why

• This module needs to support Terraform 0.14

v0.24.0

Multicert http listener @jamengual (#66)

what

• Adding SNI support

why

• variable was added but the resource was missing