missing API endpoint for ports
t0mk opened this issue · 0 comments
t0mk commented
Devices API resources have network_ports
attribtue, populated with ports dicts. In each dict there is a href
for Port API resource e.g. /ports/63b7f385-515c-41bc-9d60-668dd3c20aa0
, but HTTP GET to such Port URL returns 404.
The port resource is properly returned for example after the bond, disbond or convert-to-layer2 API call. It would be good to have it also available from GETs.
It would be handy when, for example, checking that a bond port was indeed converted to layer2. When I GET the device resource after the convert API call, the network_type is not yet updated, probably due to dome caching in the backend.