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

device.config_template field missing from rest api #13056

Closed
rrizun opened this issue Jun 29, 2023 · 0 comments · Fixed by #13110
Closed

device.config_template field missing from rest api #13056

rrizun opened this issue Jun 29, 2023 · 0 comments · Fixed by #13110
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@rrizun
Copy link

rrizun commented Jun 29, 2023

NetBox version

v3.5.4

Python version

3.8

Steps to Reproduce

noticed that device.config_template field is missing from the rest api, e.g.,

https://demo.netbox.dev/api/dcim/devices/82/

Expected Behavior

expected to see config_template field, e.g.,

"config_template": 11,

Observed Behavior

config_template field is missing

@rrizun rrizun added the type: bug A confirmed report of unexpected behavior in the application label Jun 29, 2023
@abhi1693 abhi1693 added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Jul 6, 2023
@abhi1693 abhi1693 self-assigned this Jul 6, 2023
@abhi1693 abhi1693 added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jul 6, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants