-
Notifications
You must be signed in to change notification settings - Fork 4.3k
API - Add | Remove Routing Rules #3189
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
Conversation
It seems the test has failed |
How about replace the entire routing object? That is easier to implement and use. More over we can hot-switch some balancing strategies too. |
now should be ok |
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.
Thanks for your PR! This is an important new feature. I've made some comments. Looking forward to it
apply balancer config
hot-switch balancer and replace|append new routing configs added. |
Thanks a lot! When I have time, I will integrate #412 as the next step. (Primarily to support GetRoutingRules API) |
glad to hear that.also i will check and see how can i help with that. |
I run the command line and get this error |
"api": {
"services": [
"RoutingService"
]
},
|
Thanks |
add rules :
./xray api adrules --server=127.0.0.1:62789 c1.json c2.json
remove rules :
./xray api rmrules --server=127.0.0.1:62789 ruleTag1 ruleTag2
also add ruleTag to identify rules.