starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Extend More GraphQL Relationships #7084

New Issue
Closed
opened 2025-12-29 20:19:01 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:19:01 +01:00
Owner
Copy Link

Originally created by @arthanson on GitHub (Oct 6, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.3.3

Feature type

Change to existing functionality

Proposed functionality

Extend GraphQL relationships for more GFK models (for example cable a_terminations, b_terminations).

Each CableTermination maps a particular object to a cable (associating it with either the A or B end). The REST API includes a_terminations and b_terminations for each cable using GenericObjectSerializer.

  • L2VPN terminations work similarly to cable terminations.
  • Device components (e.g. dcim.Interface) and component templates (e.g. dcim.InterfaceTemplate) can have inventory items assigned to them.
  • Most objects in NetBox support change logging, so we probably want a way to return all ObjectChanges associated with a particular object.
  • Same as above with journal entries.
  • Several models (sites, rack, devices...) support the attachment of ImageAttachments and/or ContactAssignments.
  • Both device and VM interfaces can have IP addresses and/or FHRP groups assigned to them.
  • A VLAN group can define its scope as a region, site group, site, location, rack, cluster group, or cluster.

Use case

Allows GraphQL queries to trace through objects like cabling, matching the REST API better.

Database changes

No response

External dependencies

No response

Originally created by @arthanson on GitHub (Oct 6, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.3.3 ### Feature type Change to existing functionality ### Proposed functionality Extend GraphQL relationships for more GFK models (for example cable a_terminations, b_terminations). Each CableTermination maps a particular object to a cable (associating it with either the A or B end). The REST API includes a_terminations and b_terminations for each cable using GenericObjectSerializer. - L2VPN terminations work similarly to cable terminations. - Device components (e.g. dcim.Interface) and component templates (e.g. dcim.InterfaceTemplate) can have inventory items assigned to them. - Most objects in NetBox support change logging, so we probably want a way to return all ObjectChanges associated with a particular object. - Same as above with journal entries. - Several models (sites, rack, devices...) support the attachment of ImageAttachments and/or ContactAssignments. - Both device and VM interfaces can have IP addresses and/or FHRP groups assigned to them. - A VLAN group can define its scope as a region, site group, site, location, rack, cluster group, or cluster. ### Use case Allows GraphQL queries to trace through objects like cabling, matching the REST API better. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:19:01 +01:00
adam closed this issue 2025-12-29 20:19:01 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7084
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?