You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Getting information about serial numbers that NAV has observed in chassis and modules is crucial for integration and synchronization between NAV and various inventory management applications.
The API endpoint /netbox provides sufficient information about the chassis (singular or plurar) in an IP device, but there seems to be no endpoint that provides the same for field-replacable modules, so we are unable to cross check these devices with our inventory systems.
Describe the solution you'd like
A new /module endpoint in the API, which provides read-only information about modules that NAV has discovered (i.e. the Module ORM model). The endpoint must include:
Inline information about the related Device record: This is where information about the serial number and hw/sw/fw-revisions is kept.
Ability to filter by at least netbox (analogous to other endpoints, such as /interface).
Ability to search by serial number.
The endpoint should not inline a complete Netbox relation, but the associated Netbox' id and sysname attributes should be included.
Describe alternatives you've considered
A generic /entity endpoint, as an interface to the NetboxEntity model. However, this requirement may pop up as a separate one.
The text was updated successfully, but these errors were encountered:
by "search by serial number", does this mean supporting a api/module/?search=searchstring parameter? or do you just mean a api/module/?serialnumber=someserialnumber? I guess this is the difference of Searching and Filtering in the docs.
by "search by serial number", does this mean supporting a api/module/?search=searchstring parameter? or do you just mean a api/module/?serialnumber=someserialnumber? I guess this is the difference of Searching and Filtering in the docs.
Ah, that old confusion. I think I mean filtering, as in ?serialnumber=someserialnumber - just that the serial number isn't a property of the module itself, but of device. So following previous examples, the filter might become something like ?device__serial=someserialnumber :)
Is your feature request related to a problem? Please describe.
Getting information about serial numbers that NAV has observed in chassis and modules is crucial for integration and synchronization between NAV and various inventory management applications.
The API endpoint
/netbox
provides sufficient information about the chassis (singular or plurar) in an IP device, but there seems to be no endpoint that provides the same for field-replacable modules, so we are unable to cross check these devices with our inventory systems.Describe the solution you'd like
A new
/module
endpoint in the API, which provides read-only information about modules that NAV has discovered (i.e. theModule
ORM model). The endpoint must include:Device
record: This is where information about the serial number and hw/sw/fw-revisions is kept./interface
).The endpoint should not inline a complete
Netbox
relation, but the associated Netbox'id
andsysname
attributes should be included.Describe alternatives you've considered
A generic
/entity
endpoint, as an interface to theNetboxEntity
model. However, this requirement may pop up as a separate one.The text was updated successfully, but these errors were encountered: