-
Notifications
You must be signed in to change notification settings - Fork 4.6k
feat(payments): change lookup for find gsm code and message #10585
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
base: main
Are you sure you want to change the base?
Conversation
…low identifiers and change lookup for find gsm code and message
Changed Files
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #10585 +/- ##
=======================================
Coverage ? 6.45%
=======================================
Files ? 1254
Lines ? 313246
Branches ? 0
=======================================
Hits ? 20205
Misses ? 293041
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| connector_name, | ||
| REVENUE_RECOVERY.to_string(), | ||
| REVENUE_RECOVERY, | ||
| crate::consts::DEFAULT_SUBFLOW_STR, |
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.
Did we add GSM records for REVENUE_RECOVERY flow as well? cc: @srujanchikke
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.
Yes we did in v2 prod.
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.
Are we modifying the GSM fetch logic for V2 as well? @ayush22667
| error_message.clone(), | ||
| payout_data.payout_attempt.connector.clone(), | ||
| consts::PAYOUT_FLOW_STR, | ||
| crate::consts::DEFAULT_SUBFLOW_STR, |
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.
Did we add GSM records for Paupits flow?
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.
In prod we don't have gsm records for but in sandbox we have gsm records for payout flow
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.
We may have to add those records as well then
| Some(err.message.clone()), | ||
| connector.connector_name.to_string(), | ||
| consts::REFUND_FLOW_STR.to_string(), | ||
| consts::REFUND_FLOW_STR, |
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.
Did we add GSM records for Refunds flow?
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.
In prod we don't have gsm records for but in sandbox we have gsm records for refunds flow
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.
We may have to add those records as well then
…t response tracking
Type of Change
Description
Refactored GSM (Gateway Status Map) lookup system to properly model
flowandsubflowparameters instead of using hardcoded values.Previously, the GSM table lookup used a hardcoded string
"sub_flow"for the subflow parameter. This has been refactored to properly model the flow hierarchy where:Additional Changes
Motivation and Context
closes #10584
How did you test it?
Response:
Checklist
cargo +nightly fmt --allcargo clippy