Releases: lablabs/terraform-aws-cloudtrail
Releases · lablabs/terraform-aws-cloudtrail
v0.4.0
What's changed
- fix: bumping version of s3-log-storage module to 1.4.2 to avoid this error.
v0.3.0
What's Changed
Features
- Module update by @tomas-balaz in #4
Breaking changes:
- Multiple bucket-related variables has been deleted:
bucket_expiration_days
bucket_lifecycle_prefix
bucket_lifecycle_tags
bucket_standard_transition_days
bucket_enable_glacier_transition
bucket_glacier_transition_days
- These variables were replaced with variable
bucket_lifecycle_configuration_rules
Changes:
- Update versions of included modules to the latest (
cloudtrail
,s3-log-storage
,kms-key
) - Create new kms-related variables:
trail_kms_key_usage
trail_kms_customer_master_key_spec
trail_kms_multi_region
- Update required terraform version and AWS provider version
- Update workflows
- Update README
New Contributors
- @tomas-balaz made their first contribution in #4
Full Changelog: v0.2.0...v0.3.0
v0.2.0
What's changed
Features
- use tf module
cloudposse/s3-log-storage
instead ofcloudposse/cloudtrail-s3-bucket
, by @MonolithProjects (#3) - add support for AWS Terraform provider v4 , by @MonolithProjects (#3)
Warning
Upgrade to this release may lead to potential data loss. Please follow the instructions in the link before you upgrade this module.
In addition to the changes above, a bug in a terraform module
lablabs/cloudtrail v0.1.2
cause that the cloudtrail S3 bucket was deployed with incorrect name. The new release oflablabs/cloudtrail v0.2.0
fixed the issue but Terraform is forcing to recreate the S3 bucket. Therefore there are several manual steps you have to do prior the upgrade:
- The
cloudtrail S3 bucket
,cloudtrail S3 bucket ACL
,cloudtrail S3 bucket Policy
andcloudtrail S3 Bucket side encyption configuration
have to be removed from the Terraform state file.- Run Terraform apply to create a new S3 Bucket
- Move the data from the old S3 bucket to the new one
- You can delete the old S3 bucket