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

Site status is not exposed via /api/dcim/_choices #2191

Closed
ebusto opened this issue Jun 24, 2018 · 2 comments
Closed

Site status is not exposed via /api/dcim/_choices #2191

ebusto opened this issue Jun 24, 2018 · 2 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@ebusto
Copy link

ebusto commented Jun 24, 2018 •
edited
Loading

Issue type
[ ] Feature request
[X] Bug report
[ ] Documentation

NetBox version: v2.3.4
Description
The possible choices for the site status are not exposed via /api/dcim/_choices.
@jeremystretch
Copy link
Member

Thank you for your interest in NetBox. We require that all issues be submitted using the template provided here. This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!

@jeremystretch jeremystretch added the status: revisions needed This issue requires additional information to be actionable label Jun 25, 2018
@ebusto
Copy link
Author

ebusto commented Jun 26, 2018

Similarly, interface mode is not exposed.

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation and removed status: revisions needed This issue requires additional information to be actionable labels Jun 26, 2018
@jeremystretch jeremystretch mentioned this issue Jul 2, 2018
Merged
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 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: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebusto @jeremystretch