v3.3.2

3.3.2 (2024-09-30)

Bug Fixes

• Work around limit in lambda policy size (201d6c3)

v3.3.1

3.3.1 (2024-02-19)

Bug Fixes

• bump datadog forwarder version (3678529)

v3.3.0

3.3.0 (2024-02-15)

Features

• Switch to for_each for log forwarding resources (0781beb)

v3.2.2

3.2.2 (2023-08-16)

Bug Fixes

• enforce only minimum version of terraform (7195f64), closes #55

v3.2.1

3.2.1 (2023-07-20)

Bug Fixes

• Truncate statement_id length after 100 characters (#54) (3f98ed3)

v3.2.0

3.2.0 (2023-07-17)

Features

• remove terraform resource for ELB bucket ACL configuration (terraform-only change) (fc770ec)
  • When upgrading, it will look like the ACL is being destroyed. The terraform state for the ACL will be destroyed, but the ACL itself will not. See #56 for additional details.

v3.1.1-alpha.2

3.1.1-alpha.2 (2023-07-11)

Bug Fixes

• limit statement_id length to 100 chars (6c32ece)

v3.1.1-alpha.1

3.1.1-alpha.1 (2023-07-11)

Bug Fixes

• Remove private ACL terraform resource. (b50ccb2)

v3.1.0

3.1.0 (2023-01-26)

Features

• enable support for Terraform 1.3.x (#51) (1d4c786)

v3.0.0

3.0.0 (2022-04-05)

• feat!: enable support for aws provider 4.0+ (#49) (5bc98cb), closes #49

BREAKING CHANGES

• This release drops support for AWS provider <4.0

When updating to this version, the diff will show each of the new resources as needing to be created. However, each of the new aws_s3_bucket_* resources relies on S3 API calls that utilize a PUT action in order to modify the target S3 bucket. Because these API calls adhere to standard HTTP methods for REST APIs, they should handle situations where the target configuration already exists (as noted in the HTTP RFC). Given that this is the case, it's not strictly necessary to import any new aws_s3_bucket_* resources that are a one-to-one translation from previous versions of the AWS provider -- on the next terraform apply, they'll attempt the PUT, and update the state with the results as necessary.