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.

Sign up for GitHub

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

Jump to bottom

Add connection_status to nested representation of console/power/interface components #2648

Closed
jeremystretch opened this issue Dec 6, 2018 · 0 comments
Closed

Add connection_status to nested representation of console/power/interface components #2648

jeremystretch opened this issue Dec 6, 2018 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@jeremystretch
Copy link
Member

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5-beta2

Proposed Functionality

Include the connection_status as a ChoiceField in the nested API representation of connectable device components.

Use Case

This field will likely be needed to display components in certain contexts; for example, when determining whether an interface is connected. There is no additional database overhead for returning this information, as it is stored locally on each object.

Database Changes

None

External Dependencies

None
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application API change labels Dec 6, 2018
jeremystretch added a commit that referenced this issue Dec 6, 2018
@jeremystretch
Closes #2648: Include the connection_status field in nested represena…
64d37cd 
…tions of connectable device components
@jeremystretch jeremystretch mentioned this issue Dec 10, 2018
Merged
@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.
Assignees
No one assigned
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremystretch