[RHCLOUD-22813] Message link migration #3229
Open
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
CamelProcessor tests and db migration not completed yet
This was referenced Jan 7, 2025
jessicarod7
force-pushed
the
RHCLOUD-22813-migration
branch
from
5fd95dc to
7ffe725
Compare
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.
Jira issue
https://issues.redhat.com/browse/RHCLOUD-22813
Breaking changes
This is the second part of #3221, splitting the two breaking changes into a separate PR:
data.environment_urlfromEngineToConnectormessages for PagerDuty and CamelProcessor (Google Chat, Slack, Microsoft Teams)V1.110.0Note
One change has been made to the existing format: Camel messages no longer contain a leading
\n. This caused unexpected failures while testing the Slack processor, and weirdly did not fail with the Teams processor when it should have.