-
Notifications
You must be signed in to change notification settings - Fork 707
map RESOLVE incident intent to ACTIVE incident state #39815
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
Conversation
🧪 Flaky Tests Summary👻 Haunted Tests — They Fail When No One's Watching
If the changes affect this area, please check and fix before merging. |
|
🚨 This PR needs attention 🚨 This PR is currently 114 commits behind the main branch (threshold: 50). Please update your branch before this PR can be merged. |
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 @EuroLew , thank you for the fix
💭 @tmetzke has suggested that the exporter should not process the records with this RESOLVE intent, cause it is coming from a command rather than a change of the actual state of the incident itself.
Can we consider updating PostImporterQueueFromIncidentHandler, and make handlesRecord check that the intent is different from RESOLVE, or better, that it is one of a Set of supported intents. This should prevent the problem where a zeebe intent is not handled as an incident state, in the Incident Update job
031fc8f to
87da97b
Compare
RomanJRW
left a comment
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.
I think the changes are fine, but there is an open question here that I would appreciate an answer on as it might resolve multiple open issues we have right now
webapps-schema/src/main/java/io/camunda/webapps/schema/entities/incident/IncidentState.java
Show resolved
Hide resolved
87da97b to
092baab
Compare
|
Successfully created backport PR for |
Description
The client side does not know of any incident status
RESOLVE, therefore it should instead map aRESOLVEincident intent to anACTIVEincident status.Related issues
closes #37288