[COST-5020] Use org_id for kafka message key in subs processing #5115
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
cgoodfred
added
the
smoke-tests
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5115 +/- ##
=======================================
- Coverage 94.2% 94.2% -0.0%
=======================================
Files 378 378
Lines 31624 31624
Branches 3756 3756
=======================================
- Hits 29782 29779 -3
- Misses 1174 1177 +3
Partials 668 668 |
|
/retest |
djnakabaale
approved these changes
May 20, 2024
samdoran
approved these changes
May 21, 2024
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 Ticket
COST-5020
Description
This change will use the org_id for the message key when producing kafka messages for subs consumption.
Testing
Release Notes