Update Terraform cloudposse/s3-bucket/aws to v0.49.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	minor	0.44.1 -> 0.49.0

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v0.49.0

Compare Source

Manual intervention needed

See Upgrading to v0.48.0 and AWS provider version 4.x for details about actions you will need to take when updating to this version related to upgrading to AWS provider v4.x.

Breaking changes

In order to fix #​102 (following Hashicorp's advice), this release changes the privileged_principal_arns input from a map(list(string)) to a list(map(list(string))). Where you previously input one map, like

{
  arn1 = ["prefix1/", "prefix2/"]
  arn2 = ["prefix3/]
}

you now provide a list of maps, each one mapping a single ARN to a list of prefixes:

[{
  arn1 = ["prefix1/", "prefix2/"]
}, {
  arn2 = ["prefix3/]
}]

🚀 Enhancements

Full support for lifecycle configuration

The new lifecycle_configuration_rules input allows you to specify all the options the AWS provider supports. See the example for more details.

Full support for lifecycle configuration @​Nuru (#​135)

##### what && why - Breaking change: convert `privileged_principal_arns` input to list. - Fixes #​102 - Add `lifecycle_configuration_rules` input closely matching Terraform provider arguments to fully support features. - Resolves #​87 - Resolves #​130 - Remove `acl_grants` input added in #​131, because the old `grants` input is more convenient and more powerful. ##### references - [Upgrade instructions](https://togithub.com/cloudposse/terraform-aws-s3-bucket/wiki/Upgrading-to-v0.48.0-and-AWS-provider-version-4.x) - https://github.com/hashicorp/terraform-provider-aws/issues/23375

v0.48.0

Compare Source

This release is an early release in order to unblock people who are blocked because v0.47.0 does not work with AWS Provider v4. However, the newly introduced lifecycle_configuration_rules will be replaced in the next release with a more flexible (and completely incompatible) structure that supports the evolving variety of storage options AWS provides. For this reason, we recommend users continue to use the Deprecated lifecycle_rules input for now, and anticipate it will be supported for a considerable length of time going forward.

See Upgrading to v0.48.0 and AWS provider version 4.x for details about actions you will need to take when updating to this version.

🚀 Enhancements

Upgrade to v4 aws provider @​nitrocode (#​131)

##### what * [x] Upgrade to v4 aws provider * Deprecated `policy` in favor of `source_policy_documents`, closes #​124 * Deprecated `grants` in favor of `acl_grants` * Deprecated `lifecycle_rules` in favor of `lifecycle_configuration_rules` * [x] All tests pass * [x] Current tests pass * [ ] Tests do not check website inputs. The `website_inputs` is unavailable in the tests. * [ ] Tests do not check cors. The `cors_rule_inputs` is available but unused. * [x] Backwards compatible - Is it possible to make it backwards compatible ? * [x] Generate the lifecycle rule ids ? * [x] Translate the `grant.permissions` into separate `grant.permission` blocks ? * Migration document in [this repo's Wiki](https://togithub.com/cloudposse/terraform-aws-s3-bucket/wiki/Upgrading-to-v0.48.0-and-AWS-provider-version-4.x) ##### why * Current version incompatible with AWS provider v4.x

│ Error: Unsupported attribute
│ 
│   on .terraform-mdev/modules/s3_bucket/main.tf line 166, in resource "aws_s3_bucket" "default":
│  166:         for_each = local.s3_replication_rules == null ? [] : local.s3_replication_rules
│ 
│ This object does not have an attribute named "s3_replication_rules".

• One upgraded to version 4.x, module no longer works with AWS provider 3.x
• Pin to >= 4.2.0 because of relevant bug fixes needed by this module

references

• Closes https://github.com/cloudposse/terraform-aws-s3-bucket/issues/132
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-4-upgrade
• https://github.com/hashicorp/terraform-provider-aws/releases/tag/v4.0.0
• Versions
  • https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3\_bucket
  • https://registry.terraform.io/providers/hashicorp/aws/3.74.1/docs/resources/s3\_bucket
• Some of the individual resources
  • https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3\_bucket_cors_configuration
  • https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3\_bucket_website_configuration

notes

• grants is now deprecated, but still supported. New input replacing it is acl_grants. The only difference is that grants takes a list of permissions and acl_grants takes a single permission. The only reason we are making grants deprecated is so that our inputs track the AWS resource inputs.
• lifecycle_rules is now deprecated but still supported, replaced with lifecycle_configuration_rules, which is identical except that lifecycle_configuration_rules has an id for each rule, which is now required by the AWS resource (doc). This module supplies an id for lifecycle_rules.
• aws_s3_bucket_lifecycle_configuration requires a static rules.filter element due to https://github.com/hashicorp/terraform-provider-aws/issues/23299

v0.47.1

Compare Source

• Ease refactoring by adding backward compatible lifecycle IDs (#​134)
• Pin AWS Provider to version 3.x

v0.47.0

Compare Source

🚀 Enhancements

Feat: Enable Replication Metrics @​max-lobur (#​116)

##### what * Enable replication metrics by default * Allow override via variables

AWS provider requirements update due to: https://github.com/hashicorp/terraform-provider-aws/pull/21901

why

• To be able to track replication status

references

https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-metrics.html

v0.46.0

Compare Source

🚀 Enhancements

Enable bucket key for reducing the cost of SSE-KMS with Amazon S3 @​bkmnaidu (#​115)

Signed-off-by: Krishna Mohan Bandi [email protected]

what

• Allow S3 bucket key to be enabled to reduce the cost of SSE-KMS usage with Amazon S3

why

• When KMS encryption is enabled for an Amazon S3 bucket, there is a limit on the number of KMS API calls that can be made. Enabling bucket key not only allows to reduce the number of KMS API calls but also reduces the cost of SSE-KMS with Amazon S3.

references

• https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucket-key.html
• closes #​114

##### 🐛 Bug Fixes

Fix: Change `s3_object_ownership` Description to Reflect All Possible Values @​korenyoni (#​127)

##### what - Fix `s3_object_ownership` description to reflect all possible values. ##### why - The `s3_object_ownership` variable description does not reflect all possible values. ##### references * N/A

Remove unused variable `abort_incomplete_multipart_upload_days` @​adamantike (#​92)

##### What Remove variable `abort_incomplete_multipart_upload_days`. ##### Why The `abort_incomplete_multipart_upload_days` variable isn't being used since the introduction of `lifecycle_rules` in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/85. ##### Notes

closes #​128

v0.45.0

Compare Source

feat: add delete_marker_replication_status in replication rules @​DesmondH0 (#​126)

##### what * There are no control ability for enable `Delete marker replication` in this module ##### why * The reason of this was because empty `filter` would always be generated in this [line](https://togithub.com/cloudposse/terraform-aws-s3-bucket/blob/816e61ab796a159e9f949350a1645576761dad8a/main.tf#L208) * And this will disable the `Delete marker replication` option in replication rule ##### references * https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket#delete_marker_replication_status

v0.44.2

Compare Source

🚀 Enhancements

Bump module versions and update GitHub workflows @​aknysh (#​125)

##### what * Bump module versions and update GitHub workflows ##### why * Keep up to date

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[mergify]

This pull request is now in conflict. Could you fix it @renovate[bot]? 🙏

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing, however it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.