-
Notifications
You must be signed in to change notification settings - Fork 19
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
BB-598 Validate Kafka messages against all bucket notification rules #2526
Conversation
Hello nicolas2bert,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
ping |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command:
Alternatively, the |
/create_integration_branches |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/8.5/bugfix/BB-598/notification origin/development/8.5
$ git merge origin/bugfix/BB-598/notification
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/8.5/bugfix/BB-598/notification The following options are set: create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
@bert-e approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue BB-598. Goodbye nicolas2bert. The following options are set: approve, create_integration_branches |
This PR addresses an issue in the bucket notification queue processor where consumed Kafka messages were only being validated against the first defined bucket notification rule (for a given destination queue:
queueArn
).So, notifications were not being sent out for objects/versions that matched the other defined rules.
Fix details: