-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat(core): diesel models and db interface changes for call_back_mapper table #6571
base: main
Are you sure you want to change the base?
Conversation
Changed Files
|
…witch into add-call-back-mapper-table
pub id: String, | ||
#[serde(rename = "type")] | ||
pub type_: String, | ||
pub data: serde_json::Value, |
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.
pub data: serde_json::Value, | |
pub data: pii::SecretSerdeValue, |
@@ -0,0 +1,48 @@ | |||
use error_stack::report; | |||
// use diesel_models::call_back_mapper; |
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.
Please remove this if not required
}; | ||
|
||
#[async_trait::async_trait] | ||
pub trait CallBackMapperInterface { |
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.
Can we please move the trait CallBackMapperInterface to hyperswitch_domain_models and have the domain models defined for CallBackMapper?
@@ -0,0 +1,8 @@ | |||
-- Your SQL goes here | |||
CREATE TABLE IF NOT EXISTS call_back_mapper ( |
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.
nit
CREATE TABLE IF NOT EXISTS call_back_mapper ( | |
CREATE TABLE IF NOT EXISTS callback_mapper ( |
Type of Change
Description
Created call_back_mapper table and implemented interface for DB operations.
this is added for network tokenization webhooks feature. Since this is generic, any kind of data (excluding sensitive info) can be stored.
db changes -
Network tokenization webhook feature use case - no merchant id is passed from token requestor, so network_token_requestor_ref_id is stored in this table along with merchant_id
Additional Changes
Motivation and Context
How did you test it?
This PR is only meant for creating new call_back_mapper table and doesn't interfere with any existing flows.
Checklist
cargo +nightly fmt --all
cargo clippy