GraphQL Circuit model relationship mapping to CircuitTermination

[ryanmerolle]

NetBox version

v3.0.0

Feature type

Change to existing functionality

Proposed functionality

Given the below graphql query in demo.netbox.dev

{
  circuit_list(cid: "KDPO0597") {
    id
    cid
    terminations {
      id
      term_side
      site {
        name
      }
      port_speed
      xconnect_id
      provider_network {
        id
      }
      xconnect_id
      pp_info
      description
      last_updated
    }
  }
}

Use case

I would like to be able to query cable_peer or connected_enpoints under terminations in order to query the termination details for each circuit. Currently, you can only go as far as get the pertinent info inside the circuit termination model and not the connected_endpoint specific info.

Database changes

N/A

External dependencies

N/A

[ryanmerolle]

This is pretty much in the same realm of #6829

[ryanmerolle]

I am getting closer:

{
  circuit_list(cid: "KDPO0597") {
    id
    cid
    terminations {
      id
      term_side
      cable {
        termination_a_type {
          app_label
          model
        }
        termination_a_id
        _termination_a_device {
          name
        }
        termination_b_type {
          app_label
          model
        }
        termination_b_id
        _termination_b_device {
          name
        }
      }
      site {
        name
      }
      port_speed
      xconnect_id
      provider_network {
        name
      }
      xconnect_id
      pp_info
      description
      last_updated
    }
  }
}

I do not see the termination_b or termination_a name in the models. If this needs to move to a discussion instead of an issue, I'm fine with that. I am just preemptively testing some common graphql queries I suspect users will look to leverage.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

[github-actions]

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.