Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Terraform cloudposse/s3-log-storage/aws to v0.26.0 #71

Merged
merged 5 commits into from
Apr 4, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 27, 2021

WhiteSource Renovate

This PR contains the following updates:

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

Release Notes

cloudposse/terraform-aws-s3-log-storage

v0.26.0

Compare Source

Add S3 bucket ownership controls @​max-lobur (#​61) #### what * Set aws_s3_bucket_ownership_controls to BucketOwnerPreferred #### why * Per [docs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html) this setting will let object uploader decide ownership. If `bucket-owner-full-control` ACL is specified, the bucket account take ownership, otherwise the writer account keeps ownership. Bucket on its side may enforce presence of the `bucket-owner-full-control` ACL which we already do when needed. So this setting was the only missing piece to make ownership work like we expected * I found no use cases for the other value of this resource: `ObjectWriter`. It corresponds to legacy S3 behavior which was broken for us. Decided to always set to `BucketOwnerPreferred` and not allow to customize. If the owner must be preserved, we should not pass `bucket-owner-full-control` - this is a more clear way to control the behavior. #### references * https://aws.amazon.com/blogs/storage/enforcing-ownership-of-amazon-s3-objects-in-a-multi-account-environment/ * https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html * https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_ownership_controls#ObjectWriter

v0.25.0

Compare Source

Add support for bucket notifications @​max-lobur (#​60) #### what * Add support for bucket notifications * Only SQS destination for now #### why * To enable log collection

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.

@renovate renovate bot requested review from a team as code owners September 27, 2021 16:21
@renovate renovate bot added the auto-update This PR was automatically generated label Sep 27, 2021
@renovate renovate bot requested a review from a team as a code owner September 27, 2021 16:22
@renovate renovate bot requested review from dotCipher and dylanbannon September 27, 2021 16:22
@mergify
Copy link

mergify bot commented Nov 20, 2021

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

@renovate renovate bot changed the title Update Terraform cloudposse/s3-log-storage/aws to v0.25.0 Update Terraform cloudposse/s3-log-storage/aws to v0.26.0 Dec 7, 2021
@renovate renovate bot force-pushed the renovate/cloudposse-s3-log-storage-aws-0.x branch from 90d98ff to 2411bd4 Compare December 7, 2021 07:16
Copy link

@bridgecrew bridgecrew bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️   Due to 2411bd4 - Update Terraform cloudposse/s3-log-storage/aws to v0.26.0 - 1 error was fixed.

Change details

Error ID Change Path Resource
BC_AWS_GENERAL_31 Fixed /launch-template.tf aws_launch_template.default

Copy link

@bridgecrew bridgecrew bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️   Due to 772940d - Auto Format - 1 error was fixed.

Change details

Error ID Change Path Resource
BC_AWS_GENERAL_31 Fixed /launch-template.tf aws_launch_template.default

Copy link

@cloudposse-mergebot cloudposse-mergebot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've automatically approved this PR because the checks from the automated Pull Request have passed.

@renovate renovate bot requested a review from a team as a code owner April 3, 2022 06:26
@Nuru Nuru added the no-release Do not create a new release (wait for additional code changes) label Apr 3, 2022
Nuru
Nuru previously requested changes Apr 3, 2022
Copy link
Contributor

@Nuru Nuru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update all workflows, do not auto-release, merge other PRs first.

@mergify mergify bot dismissed Nuru’s stale review April 4, 2022 02:16

This Pull Request has been updated, so we're dismissing all reviews.

Copy link

@bridgecrew bridgecrew bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️   Due to 646ebda - Pin AWS provider to < 4, update tests - 1 new error was added

Change details

Error ID Change Path Resource
BC_VUL_2 Added /test/src/go.sum Vulnerable go.sum

Copy link

@cloudposse-mergebot cloudposse-mergebot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've automatically approved this PR because the checks from the automated Pull Request have passed.

@Nuru Nuru self-requested a review April 4, 2022 02:43
@Nuru Nuru merged commit 1041406 into master Apr 4, 2022
@Nuru Nuru deleted the renovate/cloudposse-s3-log-storage-aws-0.x branch April 4, 2022 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-update This PR was automatically generated no-release Do not create a new release (wait for additional code changes)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants