feat(billing): Generate and add idempotency key to outcomes message #78795
+322
−51
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
github-actions
bot
added
the
Scope: Backend
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #78795 +/- ##
==========================================
- Coverage 78.25% 78.25% -0.01%
==========================================
Files 7105 7105
Lines 313227 313284 +57
Branches 51135 51146 +11
==========================================
+ Hits 245127 245156 +29
- Misses 61742 61764 +22
- Partials 6358 6364 +6 |
dashed
force-pushed
the
billing/outcomes-idempotency-key
branch
from
d743f49
to
b4d9cf6
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.
Add
idempotency_keyfield to outcome messages that get published to Kafka consumers (outcomes and billing outcomes).This is the first step in making outcome messages idempotent, so that we prevent duplicated usage counts when reprocessing outcome messages more than once.