search

cloudposse / terraform-aws-tfstate-backend

Terraform module that provision an S3 bucket to store the `terraform.tfstate` file and a DynamoDB table to lock the state file to prevent concurrent modifications and state corruption.
https://cloudposse.com/accelerate
Apache License 2.0
408 stars 177 forks source link

Update Terraform cloudposse/s3-log-storage/aws to v1.3.1 (release/v0) #134

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
cloudposse/s3-log-storage/aws (source) module minor 1.1.0 -> 1.3.1

Release Notes

cloudposse/terraform-aws-s3-log-storage ### [`v1.3.1`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.3.1) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.3.0...1.3.1) #### 🚀 Enhancements
Update Terraform cloudposse/s3-bucket/aws to v3.1.1 (master) @​renovate (#​88) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [cloudposse/s3-bucket/aws](https://registry.terraform.io/modules/cloudposse/s3-bucket/aws) ([source](https://togithub.com/cloudposse/terraform-aws-s3-bucket)) | module | patch | `3.1.0` -> `3.1.1` | *** ##### Release Notes
cloudposse/terraform-aws-s3-bucket ##### [`v3.1.1`](https://togithub.com/cloudposse/terraform-aws-s3-bucket/releases/tag/3.1.1) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-bucket/compare/3.1.0...3.1.1) ##### 🐛 Bug Fixes
Revert change to Transfer Acceleration from #&#​8203;178 @​&#​8203;Nuru (#&#​8203;180) ##### what - Revert change to Transfer Acceleration from [#​178](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/178) ##### why - Transfer Acceleration is not available in every region, and the change in [#​178](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/178) (meant to detect and correct drift) does not work (throws API errors) in regions where Transfer Acceleration is not supported
***
#### 🤖 Automatic Updates
Update Terraform cloudposse/s3-bucket/aws to v3.1.1 (master) @​renovate (#​88) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [cloudposse/s3-bucket/aws](https://registry.terraform.io/modules/cloudposse/s3-bucket/aws) ([source](https://togithub.com/cloudposse/terraform-aws-s3-bucket)) | module | patch | `3.1.0` -> `3.1.1` | *** ##### Release Notes
cloudposse/terraform-aws-s3-bucket ##### [`v3.1.1`](https://togithub.com/cloudposse/terraform-aws-s3-bucket/releases/tag/3.1.1) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-bucket/compare/3.1.0...3.1.1) ##### 🐛 Bug Fixes
Revert change to Transfer Acceleration from #&#​8203;178 @​&#​8203;Nuru (#&#​8203;180) ##### what - Revert change to Transfer Acceleration from [#​178](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/178) ##### why - Transfer Acceleration is not available in every region, and the change in [#​178](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/178) (meant to detect and correct drift) does not work (throws API errors) in regions where Transfer Acceleration is not supported
***
### [`v1.3.0`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.3.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.2.0...1.3.0) #### 🚀 Enhancements
Enhance lifecycle object with optionals, limit length of bucket name @​Nuru (#​87) #### what - Limit length of auto-generated bucket name to match AWS-imposed limit - Enhance `lifecycle_configuration_rules` to be fully defined with optional members #### why - Avoid situation where module fails because auto-generated bucket name is too long - Make it easier to build a list of rules #### references - https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html - [https://github.com/cloudposse/terraform-aws-s3-bucket/issues/167](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/167)
### [`v1.2.0`](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.2.0): Support new AWS S3 defaults (ACL prohibited) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-log-storage/compare/1.1.0...1.2.0) #### 🤖 Automatic Updates
Update Terraform cloudposse/s3-bucket/aws to v3.1.0 @​renovate (#​85) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [cloudposse/s3-bucket/aws](https://registry.terraform.io/modules/cloudposse/s3-bucket/aws) ([source](https://togithub.com/cloudposse/terraform-aws-s3-bucket)) | module | minor | `3.0.0` -> `3.1.0` | *** ##### Release Notes
cloudposse/terraform-aws-s3-bucket ##### [`v3.1.0`](https://togithub.com/cloudposse/terraform-aws-s3-bucket/releases/tag/3.1.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-bucket/compare/3.0.0...3.1.0)
Make compatible with new S3 defaults. Add user permissions boundary. @​&#​8203;Nuru (#&#​8203;178) ##### what - Make compatible with new S3 defaults by setting S3 Object Ownership before setting ACL and disabling ACL if Ownership is "BucketOwnerEnforced" - Add optional permissions boundary input for IAM user created by this module - Create `aws_s3_bucket_accelerate_configuration` and `aws_s3_bucket_versioning` resources even when the feature is disabled, to enable drift detection ##### why - S3 buckets with ACLs were failing to be provisioned because the ACL was set before the bucket ownership was changed - Requested feature - See [#​171](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/171) ##### references - Closes [#​174](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/174) - Supersedes and closes [#​175](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/175) - Supersedes and closes [#​176](https://togithub.com/cloudposse/terraform-aws-s3-bucket/issues/176)
Always include `aws_s3_bucket_versioning` resource @​&#​8203;mviamari (#&#​8203;172) ##### what - Always create an `aws_s3_bucket_versioning` resource to track changes made to bucket versioning configuration ##### why - When there is no `aws_s3_bucket_versioning`, the expectation is that the bucket versioning is disabled/suspend for the bucket. If bucket versioning is turned on outside of terraform (e.g. through the console), the change is not detected by terraform unless the `aws_s3_bucket_versioning` resource exists. ##### references - Closes #​171
Add support for permission boundaries on replication IAM role @​&#​8203;mchristopher (#&#​8203;170) ##### what - Adds support for assigning [permission boundaries](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) to the replication IAM role ##### why - Our AWS environment enforces permission boundaries on all IAM roles to follow AWS best practices with security. ##### references - [AWS IAM Access Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html)
##### 🤖 Automatic Updates
Update README.md and docs @​&#​8203;cloudpossebot (#&#​8203;164) ##### 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
***

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

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

renovate[bot] commented 1 year ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.