Skip to content

revert(s3): add EventBridge bucket notifications (#18150)#18507

Merged
mergify[bot] merged 4 commits intoaws:masterfrom
yerzhan7:revert-s3-eventbridge
Jan 19, 2022
Merged

revert(s3): add EventBridge bucket notifications (#18150)#18507
mergify[bot] merged 4 commits intoaws:masterfrom
yerzhan7:revert-s3-eventbridge

Conversation

@yerzhan7
Copy link
Copy Markdown
Contributor

This reverts commit 912aeda.

Why?

PR#18150 was merged prematurely (See comments). To avoid customer confusion this PR reverts it.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Jan 18, 2022

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jan 18, 2022

Title does not follow the guidelines of Conventional Commits. Please adjust title before merge.

@github-actions github-actions bot added the @aws-cdk/aws-s3 Related to Amazon S3 label Jan 18, 2022
@yerzhan7 yerzhan7 changed the title Revert "feat(s3): add EventBridge bucket notifications (#18150)" revert(s3): add EventBridge bucket notifications (#18150) Jan 18, 2022
@otaviomacedo otaviomacedo added the pr-linter/exempt-breaking-change The PR linter will not require stability in stable modules label Jan 18, 2022
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jan 19, 2022

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 348d4ca
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit 2041278 into aws:master Jan 19, 2022
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jan 19, 2022

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

rix0rrr added a commit that referenced this pull request Jan 26, 2022
In #18150, a change was merged that blew up the size of the inline
Lambda beyond its limit of 4096 characters. This change was not
detected because the Lambda constructs being used there didn't use
the regular `aws-lambda` module, but escape hatches that bypass
the regular validation (released in 1.139.0, 2.8.0).

Because this effectively broke S3 notifications, it was rolled back
in #18507 (released in 1.140.0, not yet released in 2.x line).

In this PR, add validation to make sure an event like this doesn't
happen again. This will be relevant for #18614.
mergify bot pushed a commit that referenced this pull request Jan 26, 2022
In #18150, a change was merged that blew up the size of the inline
Lambda beyond its limit of 4096 characters. This change was not
detected because the Lambda constructs being used there didn't use
the regular `aws-lambda` module, but escape hatches that bypass
the regular validation (released in 1.139.0, 2.8.0).

Because this effectively broke S3 notifications, it was rolled back
in #18507 (released in 1.140.0, not yet released in 2.x line).

In this PR, add validation to make sure an event like this doesn't
happen again. This will be relevant for #18614.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
TikiTDO pushed a commit to TikiTDO/aws-cdk that referenced this pull request Feb 21, 2022
This reverts commit 912aeda.

## Why?

[PR#18150](aws#18150) was merged prematurely (See comments). To avoid customer confusion this PR reverts it.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
TikiTDO pushed a commit to TikiTDO/aws-cdk that referenced this pull request Feb 21, 2022
In aws#18150, a change was merged that blew up the size of the inline
Lambda beyond its limit of 4096 characters. This change was not
detected because the Lambda constructs being used there didn't use
the regular `aws-lambda` module, but escape hatches that bypass
the regular validation (released in 1.139.0, 2.8.0).

Because this effectively broke S3 notifications, it was rolled back
in aws#18507 (released in 1.140.0, not yet released in 2.x line).

In this PR, add validation to make sure an event like this doesn't
happen again. This will be relevant for aws#18614.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

@aws-cdk/aws-s3 Related to Amazon S3 pr-linter/exempt-breaking-change The PR linter will not require stability in stable modules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants