Show Posts
1
23.1 Legacy Series / Using REST-API with a <uuid>
« on: June 29, 2023, 03:27:27 pm »
Hello,
we are trying to get information on routing via REST-API in order to provide a clean status for our terraform-provider running with openstack inside OVH-Cloud.
We are expecting to get a single routing from a call like this:
"curl -k --user REDACTED https://172.16.0.2/api/routes/routes/getroute?uuid=<4d99.....8ee5>
But instead a complete list of data is sent as response.
{"uuid":"ee43.....xxxx", "disabled":"0","network":"172.16.224.0\/24","gateway":"GW_IPL_Stack224 - 172.16.135.224","descr":"Route thru IPL_Transfer to IPL_Stack224_Net"},
....
"rowCount":71,"total":71,"current":1}
Are we doing something wrong ? Is it supported to get only one "entry" ?
Any hints are welcome.
regards,
Marc
we are trying to get information on routing via REST-API in order to provide a clean status for our terraform-provider running with openstack inside OVH-Cloud.
We are expecting to get a single routing from a call like this:
"curl -k --user REDACTED https://172.16.0.2/api/routes/routes/getroute?uuid=<4d99.....8ee5>
But instead a complete list of data is sent as response.
{"uuid":"ee43.....xxxx", "disabled":"0","network":"172.16.224.0\/24","gateway":"GW_IPL_Stack224 - 172.16.135.224","descr":"Route thru IPL_Transfer to IPL_Stack224_Net"},
....
"rowCount":71,"total":71,"current":1}
Are we doing something wrong ? Is it supported to get only one "entry" ?
Any hints are welcome.
regards,
Marc