-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix(s3-notifications): unable to delete the existing S3 event notifications #29022
Conversation
…tions and adding new event notifications on top of existing notifications
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
Exemption Request |
This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week. |
…tions and adding new event notifications on top of existing notifications
The breaking changes should be permitted to address the issues with deleting the existing S3 event notifications and adding new event notifications on top of existing notifications |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @sarangarav, we don't allow any breaking changes in stable modules, however, you can still add this fix behind a feature flag: https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md#feature-flags.
I'm not sure exactly how it would work for changes to the index.py
file but let me check with the team and get back to you. Also have you run the integ tests for s3-notifications
? And if so could you also push the test snapshots if any were changed.
@@ -45,9 +50,9 @@ def with_id(n): | |||
for t in CONFIGURATION_TYPES: | |||
if request_type == 'Update': | |||
ids = [with_id(n) for n in old.get(t, [])] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this line can be removed
Hey @sarangarav, So the
and then access that within the |
This PR has been in the BUILD FAILING state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week. |
We're experiencing this exact issue and would appreciate a fix. Please don't abandon this PR. |
This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error. |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
hey @sarangarav, are you still planning to work on this? |
Going to close this for now. Feel free to open a new PR if you would like to continue to work on this fix with the suggested changes. |
The pull request linter fails with the following errors:
PRs must pass status checks before we can provide a meaningful review. If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing ✅ A exemption request has been requested. Please wait for a maintainer's review. |
The pull request linter fails with the following errors:
PRs must pass status checks before we can provide a meaningful review. If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing ✅ A exemption request has been requested. Please wait for a maintainer's review. |
Issue # (if applicable)
Reason for this change
Fix to address the issues deleting the existing S3 event notifications and adding new event notifications on top of existing notifications.
Description of changes
We fixed the hashing logic used to identify old vs external S3 event notifications
Description of how you validated changes
Manually tested the changes
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license