You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The hypervisor API has various endpoints that allow to work with the routes, like GET /nodes/{pk}/routes/{rid}. The problem is that it is not possible to get the value that must be sent as the {rid} param, as the hypervisor API does not have an endpoint for getting the ID of the routes.
Calling the GET /nodes/{pk}/routes endpoint only returns a key property for each route, which worked before when sent as the {rid} param, but not anymore, as the API responds error: "invalid UUID length: 0".
Possible implementation
2 possible solutions are:
Add the ID to the GET /nodes/{pk}/routes endpoint.
Make the API endpoints related to the routes work if the key property returned by the GET /nodes/{pk}/routes endpoint is sent as the {rid} param.
The text was updated successfully, but these errors were encountered:
Describe the bug
The hypervisor API has various endpoints that allow to work with the routes, like
GET /nodes/{pk}/routes/{rid}
. The problem is that it is not possible to get the value that must be sent as the{rid}
param, as the hypervisor API does not have an endpoint for getting the ID of the routes.Calling the
GET /nodes/{pk}/routes
endpoint only returns akey
property for each route, which worked before when sent as the{rid}
param, but not anymore, as the API respondserror: "invalid UUID length: 0"
.Possible implementation
2 possible solutions are:
GET /nodes/{pk}/routes
endpoint.key
property returned by theGET /nodes/{pk}/routes
endpoint is sent as the{rid}
param.The text was updated successfully, but these errors were encountered: