-
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(routing): Enable volume split for dynamic routing #6662
base: main
Are you sure you want to change the base?
Conversation
…hyperswitch into feat_elimination_routing
…tch into feat_elimination_routing
…tch into dynamo-volume-split
…hyperswitch into feat_elimination_routing
…hyperswitch into feat_elimination_routing
…tch into dynamo-volume-split
…f github.com:juspay/hyperswitch into dynamo-volume-split
…tch into dynamo-volume-split
@@ -1776,6 +1776,10 @@ impl Profile { | |||
web::resource("/toggle") | |||
.route(web::post().to(routing::toggle_elimination_routing)), | |||
), | |||
) | |||
.service( | |||
web::resource("/set_volume_split") |
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.
By just looking at the api-contract, client won't be aware that he is setting volume split for dynamic routing type right? Even the query param is just split
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.
this is scoped under /dynamic_routing
Type of Change
Description
Have added a new API for enabling volume split for dynamic routing service
Additional Changes
Motivation and Context
How did you test it?
Status in DB -
Checklist
cargo +nightly fmt --all
cargo clippy