[Feature]: Add assigned_object models in GraphQL API similar to the REST API

[ryanmerolle]

NetBox version

v3.2.6

Feature type

Add a function

Proposed functionality

NetBox core graphql package does not support walking assigned_object_type/assigned_object_id approach to relations.

Use case

It would be nice to walk from ACL to assigned devices, but you cannot currently.

External dependencies

graphql-python/graphene-django

[ryanmerolle]

• Add assigned_object models in GraphQL API similar to the REST API netbox#9817

[ryanmerolle]

It looks like this was addressed with:

• Release v3.4.0 netbox#11180

In netbox_acls/api/serializers.py I marked 2 spots with # TODO to address in our NetBox 3.4 compatible plugin version.

[pheus]

I have tested assigned_object for both Device and VirtualMachine successfully. In the query, the object type must be specified using ... on DeviceType. However, as I understand the Feature Request, this is expected behavior.

Since the requested functionality is already supported, I believe this issue can be closed. If I have misunderstood the request, please let me know.

Example Query:

query MyQuery {
  access_list(id: "3") {
    id
    name
    assigned_object {
      ... on DeviceType {
        id
        name
      }
    }
  }
}

Example Response:

{
  "data": {
    "access_list": {
      "id": "3",
      "name": "Access-List-Standard1",
      "assigned_object": {
        "id": "1",
        "name": "switch-dc01"
      }
    }
  }
}