Missing GraphQL fields #17749
Labels
severity: low
Does not significantly disrupt application functionality, or a workaround is available
status: accepted
This issue has been accepted for implementation
type: bug
A confirmed report of unexpected behavior in the application
Deployment Type
Self-hosted
Triage priority
I volunteer to perform this work (if approved)
NetBox Version
v4.1.3
Python Version
3.12
Steps to Reproduce
Expected Behavior
I receive a response with a list of all (if any) devices and no errors. This is an example from a v3.7.8 instance with no devices:
Observed Behavior
I receive the following response/error:
When I first ran into this, I traced it back to the GraphQL engine switch in the v4.0 release. And because "if it happens once, it may happened twice" I grabbed the GraphQL schemas from a fresh v3.7.8 and v4.1.3 instance, and quickly wrote a script to find all fields and arguments that no longer exist; which were a lot. I had to account for general differences how these engines represent stuff, and filter out all the intended changes (like
devicetype_id
being renamed todevice_type_id
). In the end, this handful of unaccounted-for field removals was left:While I found no matching issue for the
Rack
change, it looks like a renaming that happened as part of the engine switch, and probably is fine at it is. I am not sure what theSite.asn
field was meant to be, because there also is aSite.asns: List[ASN]
field; this one is probably also fine as it is.Device
missing thedevicebays
field is the one I initially ran into, which I definitely consider a bug. And then there are the three tree-building self-referentialContactGroup
,TenantGroup
andWirelessLANGroup
which are missing their respectivechildren
field; I would also consider this a bug, since others likeLocation
still have theirchildren
field.The text was updated successfully, but these errors were encountered: