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

Add description fields to interface connections export #2810

Closed
dberube1 opened this issue Jan 28, 2019 · 1 comment
Closed

Add description fields to interface connections export #2810

dberube1 opened this issue Jan 28, 2019 · 1 comment
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@dberube1
Copy link

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.3

Proposed Functionality

Include the interface descriptions for both the A-side and B-side interfaces in the exported csv file generated from the interface connections page. Currently when you export the interface list to csv the descriptions are omitted.

I know this was originally blocked in request #614, but I feel with the added virtualization features that it would be useful to include this data on the export.

Use Case

This would be useful when giving the exported file to anyone that is having to physically work on the equipment, such as cabinet migrations, or server/switch replacement. I use the interface description heavily to document individual network interface name to the PCI slot/port on servers in my environment.

Example: in a VMware environment the physical adapters are named vmnic[0-14]. The interface name vmnic4 is not useable for tracing the physical port on the back of the server. In this case I've used the description field to indicate the following information on servers: "Card type: PCI Slot # / Port #".

Database Changes

No database changes required.

External Dependencies

No external dependencies are required.

@jeremystretch
Copy link
Member

Accepting this enhancement to maintain parity with the built-in list since custom export templates aren't supported for connection lists.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Jan 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
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

2 participants