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

Provide a method for import/export of CircuitTerminations #5230

New Issue
Closed
opened 2025-12-29 19:25:41 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:25:41 +01:00
Owner
Copy Link

Originally created by @nniehoff on GitHub (Aug 25, 2021).

NetBox version

v2.11.2

Feature type

New functionality

Proposed functionality

Allow import/export of CircuitTerminations.

Use case

As a user of NetBox there are times when I take a partial export of production data, for example, cables, circuits and devices and import this into a development install of NetBox for testing. There are reasons which I can't take a full postgres dump of the production data to this test environment. I would like to also include CircuitTerminations in this partial export for testing in a development environment.

Database changes

None

External dependencies

None

Originally created by @nniehoff on GitHub (Aug 25, 2021). ### NetBox version v2.11.2 ### Feature type New functionality ### Proposed functionality Allow import/export of CircuitTerminations. ### Use case As a user of NetBox there are times when I take a partial export of production data, for example, cables, circuits and devices and import this into a development install of NetBox for testing. There are reasons which I can't take a full postgres dump of the production data to this test environment. I would like to also include CircuitTerminations in this partial export for testing in a development environment. ### Database changes None ### External dependencies None
adam added the type: feature label 2025-12-29 19:25:41 +01:00
adam closed this issue 2025-12-29 19:25:42 +01:00
adam commented 2025-12-29 19:25:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2021):

This is probably best handled via a custom export template for circuits, or by leveraging the REST API.

@jeremystretch commented on GitHub (Oct 5, 2021): This is probably best handled via a custom export template for circuits, or by leveraging the REST API.
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 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#5230
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?