Closed coxley closed 7 years ago
I have:
set_name
to actually work on save from DRF properlya_endpoint
against z_endpoint
values and vice versa. Not sure if this would make it inefficient though since that'd be extra query at save (foreign keys)display_name
to name
GET /api/site/:id/interfaces/:id/circuit/
GET /api/site/:id/circuits/:id/devices/
GET /api/site/:id/circuits/:id/interfaces/
GET /api/site/:id/circuits/:id/addresses/
I've added validation for a_endpoint
and z_endpoint
to do the cross-over checks.
I've taken over this feature and will be replacing it with a new PR.
203
This is a first iteration. It's pretty weak, I'll admit. Even with a device or interface id, I don't think you can query the circuits like we would want. This is mostly because I lack familiarity with Django, DRF, and the existing work here.
Ideally I think we would want to be able to do:
This does work, though, for relating and browsing in the API. I mostly want to get discussion sparked here and get help with the rest.
http://imgur.com/a/Dsftn