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

display field omitted from VirtualDisk representation in REST API #15241

Closed
jeremystretch opened this issue Feb 23, 2024 · 0 comments · Fixed by #15244
Closed

display field omitted from VirtualDisk representation in REST API #15241

jeremystretch opened this issue Feb 23, 2024 · 0 comments · Fixed by #15244
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

@jeremystretch
Copy link
Member

Deployment Type

NetBox Cloud

NetBox Version

v3.7.3

Python Version

3.11

Steps to Reproduce

  1. Create one or more virtual disks assigned to a virtual machine (attributes are unimportant)
  2. Make a request for /api/virtualization/virtual-disks/

Expected Behavior

The serialized representation of each virtual disk should include a display field conveying the disk's name.

Observed Behavior

The display field is absent.

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application 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 Feb 23, 2024
@abhi1693 abhi1693 self-assigned this Feb 23, 2024
@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 Feb 23, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 24, 2024
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