Replies: 1 comment 1 reply
-
|
Hmm I can reproduce this, but looking at the codebase it's not apparent why this wouldn't work for PATCH requests while POST requests work fine. Feel free to open a bug report and I can look into it some more. There are a couple workarounds you could do in the meantime:
Thanks! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My apologies in advance if I am missing something simple, and I have searched here and elsewhere and have not found an answer.
I am trying to update the routing priority of one of my gateways in one of my gateway groups from Tier 1 to Tier 3 (basically making the gateway that is currently Tier 2 the priority gateway).
I get a success 200 when updating the priority of the target gateway from Tier 1 to Tier 3. But even after I apply the change using a POST to routing/apply the gateway priority remains unchanged (Tier 1) -- confirmed by both a GET call in the API and via the WebGUI. I am currently doing all calls via the Swagger docs, so it's not any code that I've written.
I am using JWT authentication and verified the user I am using has the following privileges (in addition to the JWT privilege), and I am not getting any authentication errors.
REST API - /api/v2/routing/gateway/group/priority PATCH Allow PATCH request to /api/v2/routing/gateway/group/priority
REST API - /api/v2/routing/gateway/group/priority GET Allow GET request to /api/v2/routing/gateway/group/priority
REST API - /api/v2/routing/apply GET Allow GET request to /api/v2/routing/apply
REST API - /api/v2/routing/apply POST Allow POST request to /api/v2/routing/apply
Beta Was this translation helpful? Give feedback.
All reactions