Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable populating bulk import data from a remote data file #11780

Closed
jeremystretch opened this issue Feb 17, 2023 · 0 comments
Closed

Enable populating bulk import data from a remote data file #11780

jeremystretch opened this issue Feb 17, 2023 · 0 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@jeremystretch
Copy link
Member

NetBox version

v3.4.4

Feature type

New functionality

Proposed functionality

NetBox v3.5 will introduce the ability to replicate data from remote sources, such as a git repository (see #11558). We can leverage this ability to streamline the bulk import process, enabling a user to select an existing remote file as an alternative to submitting a local file for upload.

The implementation I envision would comprise three tabs under the bulk import view for a model:

  • Direct import (text box)
  • File upload
  • Remote file

Under the third tab, the user can select a remote data source and the desired file, the submit the form. The remote file's data will be used in place of uploaded data. In the event of an error, we could either ask the user to select a different file, or replicate the file content under the first tab for modification.

Use case

In a scenario where the user has prepared a large amount of data to be imported, it may be quicker for them to replicate a remote repository rather than downloading and uploading each file manually.

Database changes

No response

External dependencies

No response

@jeremystretch jeremystretch added type: feature Introduction of new functionality to the application status: under review Further discussion is needed to determine this issue's scope and/or implementation beta Concerns a bug/feature in a beta release labels Feb 17, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation beta Concerns a bug/feature in a beta release labels Mar 1, 2023
@jeremystretch jeremystretch added this to the v3.5 milestone Mar 1, 2023
@jeremystretch jeremystretch self-assigned this Mar 14, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

1 participant