Releases: trussworks/terraform-aws-logs
Further improve the aws 4.0 provider upgrade path
This releases #273.
See https://github.com/trussworks/terraform-aws-logs#upgrade-paths for details on how to upgrade.
Of note, this replaces the enable_versioning boolean variable with the versioning_status string variable due to the more nuanced behavior of the aws_s3_bucket_versioning resource. With the new behavior, the AWS provider distinguishes between Disabled versioning (versioning has never been enabled) and Suspended versioning (versioning was once enabled, but is now turned off). The old behavior did not include this differentiation.
Additionally, this sets the minimum AWS provider version to 3.75.0.
Improve the upgrade experience to 12.x
Enable the use of version 4 of the AWS provider
Enable the use of version 4 of the AWS provider. Upgrading to this version will require running multiple terraform import statements. Please see the Readme for details: https://github.com/trussworks/terraform-aws-logs#upgrading-from-11xx-to-12xx
Remove Automation tagging in favor of provider default_tags
- Remove Automation tagging - The preference is to use the AWS provider
default_tagsfor settingAutomation = Terraform. If you would like to continue using Automation tagging, you can define it directly invar.tags.
Restrict to 3.x of the aws provider in anticipation of breaking changes
Expose the mfa_delete attribute
Add enable_versioning
This release adds the ability to turn on versioning for the logs bucket via the enable_versioning variable.
Relax version constraints so folks can use this module with 0.14.x
Add logging support to s3 bucket to address CIS.2.6
Beware of the logging turtles
Release off of the terraform12 branch
Merge pull request #103 from trussworks/ee-add-aws3-support Ee add aws provider v3 support to tf12 branch