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

partial database transfer #5749

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

Originally created by @someconservator on GitHub (Dec 9, 2021).

NetBox version

v3.1.0

Feature type

New functionality

Proposed functionality

Transferring data in parts from the web interface: only ipam, only virtualization, virtualization and ipam, data without custom fields, etc.

Use case

Currently, the export and subsequent import (transfer) of the database is performed entirely using the pg_dump/psql OS commands. The problem is that not the entire database needs to be transferred from time to time. For example, the same database contains custom fields. And in the event that an organization has a test and production environment, a periodic dump of the entire base of the production environment (for example, to more closely match to the test environment) leads to the need to destroy custom fields in the test environment. Therefore, it is necessary to be able to transfer the base in parts.
In addition, not all users of netbox (operators, user support) can make a partial transfer with sufficient confidence when using system commands. Or they may not have access to the terminal at all. Hence, having export/import functions in the application can also be helpful in this regard.

Database changes

No response

External dependencies

No response

Originally created by @someconservator on GitHub (Dec 9, 2021). ### NetBox version v3.1.0 ### Feature type New functionality ### Proposed functionality Transferring data in parts from the web interface: only ipam, only virtualization, virtualization and ipam, data without custom fields, etc. ### Use case Currently, the export and subsequent import (transfer) of the database is performed entirely using the pg_dump/psql OS commands. The problem is that not the entire database needs to be transferred from time to time. For example, the same database contains custom fields. And in the event that an organization has a test and production environment, a periodic dump of the entire base of the production environment (for example, to more closely match to the test environment) leads to the need to destroy custom fields in the test environment. Therefore, it is necessary to be able to transfer the base in parts. In addition, not all users of netbox (operators, user support) can make a partial transfer with sufficient confidence when using system commands. Or they may not have access to the terminal at all. Hence, having export/import functions in the application can also be helpful in this regard. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:32:12 +01:00
adam closed this issue 2025-12-29 19:32:12 +01:00
adam commented 2025-12-29 19:32:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 9, 2021):

I'm not sure what you're trying to accomplish, but it seems to be well outside the scope of normal NetBox usage. Any replication of the database, partial or otherwise, will need to be handled by an administrator and is not something that would be performed from within NetBox itself.

@jeremystretch commented on GitHub (Dec 9, 2021): I'm not sure what you're trying to accomplish, but it seems to be well outside the scope of normal NetBox usage. Any replication of the database, partial or otherwise, will need to be handled by an administrator and is not something that would be performed from within NetBox itself.
adam commented 2025-12-29 19:32:13 +01:00
Author
Owner
Copy Link

@someconservator commented on GitHub (Dec 10, 2021):

OK. We will suffer on our own. :)

@someconservator commented on GitHub (Dec 10, 2021): OK. We will suffer on our own. :)
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#5749
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?