-
Notifications
You must be signed in to change notification settings - Fork 289
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 event update logic for Kubernetes source #1122
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pkosiec
force-pushed
the
fix-update-event-logic
branch
2 times, most recently
from
July 5, 2023 10:58
78e3427
to
d9d9acf
Compare
pkosiec
force-pushed
the
fix-update-event-logic
branch
from
July 5, 2023 12:59
d9d9acf
to
abeb334
Compare
pkosiec
force-pushed
the
fix-update-event-logic
branch
from
July 5, 2023 13:38
abeb334
to
8e111ce
Compare
huseyinbabal
approved these changes
Jul 6, 2023
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.
Works as expected 👍
This was referenced Oct 10, 2023
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changes proposed in this pull request:
updateSetting.fields
are provided, ensure there's a diff between these fields.updateSetting.fields
config, route all update events.includeDiff
is true, print diff as a part of the message.Revert breaking changes in messages APIextracted to Revert API changes for api.Message #1124This bug was related to changes in our event dispatching system when extracting Kubernetes events to a separate plugin. An event was qualified to dispatch even if it didn't contain changes for the
updateSetting.Fields
.This regression was introduced in 1.0.0.
Testing
Run Botkube from this PR with the following config:
Apply sample resource, e.g. STS:
k apply sts.yaml
Edit the resource:
k edit sts web
The following fields will trigger an update event:
So you can try multiple different edits to see if they trigger the updates.
For previous Botkube, any update of such STS would trigger an event.
Related issue(s)
Resolves #1081