v0.11.0

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

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.10.3

🤖 Automatic Updates

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

This PR contains the following updates:

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

---

Release Notes

cloudposse/terraform-aws-s3-log-storage

v0.18.1

Compare Source

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​51)

#### 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.10.2

🤖 Automatic Updates

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

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.10.1

🤖 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

Compare Source

Bc compliance @​maximmi (#​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.10.0

Terraform 0.14 upgrade @maximmi (#27)

what

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

why

• Support Terraform 0.14

v0.9.0

Update to using context.tf @joe-niland (#25)

what

• Update to using new context.tf pattern
• bump upstream version of cloudposse/terraform-aws-s3-log-storage.git to 0.14.0

why

• Support streamlined context.tf variable usage
• Support AWS provider 3.0

references

• closes #23

v0.8.0

fix: update aws provider version @tirumerla (#24)

what

• Update aws provider to >= 2.0 avoid module version conflicts when used with >= 3.0 modules (eg. aws-eks-node-group).

why

• This module is being used with terraform-aws-alb & 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.7.0

• No changes

Additional TF 0.13 Fixes

what

• upgrade chatops
• add automatic releasing
• upgrade to go modules
• update any version pinning
• (locally verififed) no terraform init errors using cli

why

• Support Terraform 0.13

0.6.1

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