Skip to content

Custom field support for device components #5401

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

Closed
mngan opened this issue Dec 1, 2020 · 2 comments
Closed

Custom field support for device components #5401

mngan opened this issue Dec 1, 2020 · 2 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@mngan
Copy link

mngan commented Dec 1, 2020

Environment

  • Python version: 3.8.5
  • NetBox version: 2.9.9

Proposed Functionality

Add support for custom fields for Interfaces

Use Case

I would like to record ESI's for LAG bundles and also external id's to link to port objects in our existing DCIM.

Database Changes

Adding CustomFieldModel to the Interface/BaseInterface object hierarchy will result in schema changes, and possibly require refactoring if performance is an issue.

External Dependencies

None

@jeremystretch jeremystretch changed the title Custom Field support for Interfaces Custom field support for device components Dec 2, 2020
@jeremystretch
Copy link
Member

I've tweaked the scope of this to include all device components.

@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release type: feature Introduction of new functionality to the application labels Dec 3, 2020
@candlerb
Copy link
Contributor

candlerb commented Dec 3, 2020

Link to #1254 #2281 #2510 #2789 #3083

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Dec 21, 2020
@jeremystretch jeremystretch added this to the v2.11 milestone Dec 21, 2020
@jeremystretch jeremystretch self-assigned this Mar 1, 2021
jeremystretch added a commit that referenced this issue Mar 1, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 9, 2021
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

3 participants