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
Using GraphQL to query the API to get information would simplify a lot of scenarios that today require multiple requests to get neccessary information. Example RootQuery would be: Tenant, IP-address, Prefix, VRF, VLAN, Interface, Virtual Machine, Virtual Interface, Device.
Having these would make life very easy to extract a Tenant's logical topology in one blow.
Use Case
Minimize number of GET requests to identify ID of object in netbox based on their relations when preparing an external system to update several objects in netbox.
Database Changes
No changes would be neccessary, as the models already have relations
External Dependencies
There are a package called Graphene-Django that could do this
The text was updated successfully, but these errors were encountered:
Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #2007 for further discussion. This is not something we'll be undertaking in the near future.
Environment
Proposed Functionality
Using GraphQL to query the API to get information would simplify a lot of scenarios that today require multiple requests to get neccessary information. Example RootQuery would be: Tenant, IP-address, Prefix, VRF, VLAN, Interface, Virtual Machine, Virtual Interface, Device.
Having these would make life very easy to extract a Tenant's logical topology in one blow.
Use Case
Minimize number of GET requests to identify ID of object in netbox based on their relations when preparing an external system to update several objects in netbox.
Database Changes
No changes would be neccessary, as the models already have relations
External Dependencies
There are a package called Graphene-Django that could do this
The text was updated successfully, but these errors were encountered: