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

Include the provider in the brief REST API representation of a circuit #10164

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

Originally created by @jeremystretch on GitHub (Aug 30, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.1-beta1

Feature type

Change to existing functionality

Proposed functionality

When fetching the brief representations of circuits via the REST API (e.g. http://netbox:8000/api/circuits/circuits/?brief=true), include the nested representation of the provider for each circuit.

Use case

Each circuit must have an assigned provider, which is often necessary to fully identify an individual circuit (somewhat analogous to a device type's assigned manufacturer).

Database changes

None

External dependencies

None

Originally created by @jeremystretch on GitHub (Aug 30, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.1-beta1 ### Feature type Change to existing functionality ### Proposed functionality When fetching the brief representations of circuits via the REST API (e.g. `http://netbox:8000/api/circuits/circuits/?brief=true`), include the nested representation of the provider for each circuit. ### Use case Each circuit must have an assigned provider, which is often necessary to fully identify an individual circuit (somewhat analogous to a device type's assigned manufacturer). ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurebetacomplexity: low labels 2025-12-29 21:27:42 +01:00
adam closed this issue 2025-12-29 21:27:42 +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 beta complexity: low 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#10164
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?