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 |
yuhan6665
left a comment
There was a problem hiding this comment.
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 |
I added it on both the server and the client, but it still doesn’t work. |
add rules :
./xray api adrules --server=127.0.0.1:62789 c1.json c2.jsonremove rules :
./xray api rmrules --server=127.0.0.1:62789 ruleTag1 ruleTag2also add ruleTag to identify rules.
{ ... "routing": { ... "rules": [ { "ruleTag" : "mainRule", "outboundTag": "api", "type": "field", "inboundTag": [ "api" ] }, ...