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

Component template missing module_type API field #9330

Closed
omri-ice opened this issue May 10, 2022 · 0 comments
Closed

Component template missing module_type API field #9330

omri-ice opened this issue May 10, 2022 · 0 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@omri-ice
Copy link

NetBox version

v3.2.1

Python version

3.9

Steps to Reproduce

  1. Create a new module and module components (interface, console port, etc)
  2. Find the ID if said component and navigate to the API endpoint (for example GET /api/dcim/interface-templates/76/)
  3. The device_type is set to null and there's no module_type field

Expected Behavior

A module_type field should be present with similar information to the device_type field.

Observed Behavior

The module_type field isn't returned on API GET calls.
it should be added under the relevant component templates' fields variable

@omri-ice omri-ice added the type: bug A confirmed report of unexpected behavior in the application label May 10, 2022
@DanSheps DanSheps added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 10, 2022
@jeremystretch jeremystretch self-assigned this May 11, 2022
@jeremystretch jeremystretch 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 May 11, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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

3 participants