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

GraphQL: expose L2VPN termination in interface #11350

New Issue
Closed
opened 2025-12-29 21:44:03 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:44:03 +01:00
Owner
Copy Link

Originally created by @swoga on GitHub (Jul 8, 2025).

Originally assigned to: @swoga on GitHub.

NetBox version

v4.3.3

Feature type

New functionality

Proposed functionality

It would be convenient if the GraphQL InterfaceType could output the L2VPN temination (similar to the REST API).
therefore my proposal: add l2vpn_termination: L2VPNTerminationType to InterfaceType

Use case

I would like to use GraphQL to retrieve the interfaces of devices, including information about connected L2VPNs, in order to generate configurations for the devices.

e.g.

{
  device_list(filters: {}) {
    name
    interfaces {
      name
      l2vpn_termination: {            <---
        l2vpn {
          name
        }
      }
  }
}

Database changes

none

External dependencies

none

Originally created by @swoga on GitHub (Jul 8, 2025). Originally assigned to: @swoga on GitHub. ### NetBox version v4.3.3 ### Feature type New functionality ### Proposed functionality It would be convenient if the GraphQL `InterfaceType` could output the L2VPN temination (similar to the REST API). therefore my proposal: add `l2vpn_termination: L2VPNTerminationType` to `InterfaceType` ### Use case I would like to use GraphQL to retrieve the interfaces of devices, including information about connected L2VPNs, in order to generate configurations for the devices. e.g. ``` { device_list(filters: {}) { name interfaces { name l2vpn_termination: { <--- l2vpn { name } } } } ``` ### Database changes none ### External dependencies none
adam added the type: bugstatus: acceptedtopic: GraphQLseverity: low labels 2025-12-29 21:44:03 +01:00
adam closed this issue 2025-12-29 21:44:03 +01:00
adam commented 2025-12-29 21:44:04 +01:00
Author
Owner
Copy Link

@swoga commented on GitHub (Jul 11, 2025):

I am happy to contribute a fix, it seems to be quite easy to implement.
Please let me know if you would like me to submit a PR.

@swoga commented on GitHub (Jul 11, 2025): I am happy to contribute a fix, it seems to be quite easy to implement. Please let me know if you would like me to submit a PR.
adam commented 2025-12-29 21:44:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 14, 2025):

@swoga assigned to you, thanks!

@jeremystretch commented on GitHub (Jul 14, 2025): @swoga assigned to you, thanks!
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 severity: low status: accepted topic: GraphQL type: bug
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#11350
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?