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

API virtualmachine config_template data is missing #15070

Closed
nicolai-hornung-bl opened this issue Feb 7, 2024 · 1 comment
Closed

API virtualmachine config_template data is missing #15070

nicolai-hornung-bl opened this issue Feb 7, 2024 · 1 comment
Assignees
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@nicolai-hornung-bl
Copy link

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.8

Steps to Reproduce

Query the API Object of any VM. While the render-config endpoint was added in v3.7.1 with PR #14287 the corresponding config_template value cannot be queried or set using the API.

Expected Behavior

I want to be able to assign and query config templates to virtualmachines using the API as I am able to do with Devices and in the GUI.

Observed Behavior

The config_template key is missing.

@nicolai-hornung-bl nicolai-hornung-bl added the type: bug A confirmed report of unexpected behavior in the application label Feb 7, 2024
@jeremystretch
Copy link
Member

Looks like the field was mistakenly omitted from VirtualMachineWithConfigContextSerializer. (The base serializer has it defined.)

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows labels Feb 8, 2024
@jeremystretch jeremystretch self-assigned this Feb 8, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants