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

Ability to pass on VLAN ID in bulk CSV interface import #5764

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

Originally created by @nemo438 on GitHub (Dec 11, 2021).

NetBox version

v3.1.0

Feature type

New functionality

Proposed functionality

Have the ability to pass on the VID when importing interfaces in the initial stage.

Suggestion csv untagged mode

device,name,type,mode,untagged_vid
Switch01,Gi1/0/1,1000BASE-T (1GE),access,173

Suggestion csv tagged mode

device,name,type,mode,tagged_vid
Switch01,Gi1/0/1,1000BASE-T (1GE),access,(173,186,998)

Use case

When adding a new device, it would be nice to have the ability to import all information straight away. Sometimes it takes more time write an script to import than just to export and edit in excel.

Database changes

No response

External dependencies

No response

Originally created by @nemo438 on GitHub (Dec 11, 2021). ### NetBox version v3.1.0 ### Feature type New functionality ### Proposed functionality Have the ability to pass on the VID when importing interfaces in the initial stage. Suggestion csv untagged mode ``` device,name,type,mode,untagged_vid Switch01,Gi1/0/1,1000BASE-T (1GE),access,173 ``` Suggestion csv tagged mode ``` device,name,type,mode,tagged_vid Switch01,Gi1/0/1,1000BASE-T (1GE),access,(173,186,998) ``` ### Use case When adding a new device, it would be nice to have the ability to import all information straight away. Sometimes it takes more time write an script to import than just to export and edit in excel. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:32:23 +01:00
adam closed this issue 2025-12-29 19:32:24 +01:00
adam commented 2025-12-29 19:32:24 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Dec 18, 2021):

I don't think this can work just using the VID. This is because the VID is not unique: you can have multiple distinct broadcast domains, using the same tag.

However it could work if you gave sufficient information to identify a single VID, which would depend on your environment. e.g. {vid:173, site:"foo"} if your vid's are unique per site.

@candlerb commented on GitHub (Dec 18, 2021): I don't think this can work just using the VID. This is because the VID is not unique: you can have multiple distinct broadcast domains, using the same tag. However it could work if you gave sufficient information to identify a single VID, which would depend on your environment. e.g. `{vid:173, site:"foo"}` if your vid's are unique per site.
adam commented 2025-12-29 19:32:25 +01:00
Author
Owner
Copy Link

@nemo438 commented on GitHub (Jan 9, 2022):

Sorry for late response, GitHub notification email was stuck in spam.

I think it would work perfectly to use the {vid:173, site:"foo"} at the import phase to specify VID and site.

If the user has the possibility to export data perform the mass update and then import it again it would be great.

@nemo438 commented on GitHub (Jan 9, 2022): Sorry for late response, GitHub notification email was stuck in spam. I think it would work perfectly to use the {vid:173, site:"foo"} at the import phase to specify VID and site. If the user has the possibility to export data perform the mass update and then import it again it would be great.
adam commented 2025-12-29 19:32:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 11, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 11, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:32:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 4, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 4, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:32:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 5, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jul 5, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#5764
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?