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
The first page of 50 results works as expected. However, after retrieval of the first set of 50 machines the nextLink url is truncated to '/api/DeviceService/Devices?$skip=50&$top=50' instead of properly including the IDs listed in the original URL. This leads to automated code looping over the totality of the OME inventory instead of some list of specified IDs.
The text was updated successfully, but these errors were encountered:
- Implemented a temporary patch to resolvedell#228. Instead of allowing OME to paginate, it will manually separate the IDs into groups of 50 and then query them one at a time.
- Made the error message for using the incorrect arguments more explicit
- Added the ability to control how long the script will ping OME for the update job status before it times out.
Signed-off-by: Grant Curell <[email protected]>
- Implemented a temporary patch to resolve#228. Instead of allowing OME to paginate, it will manually separate the IDs into groups of 50 and then query them one at a time.
- Made the error message for using the incorrect arguments more explicit
- Added the ability to control how long the script will ping OME for the update job status before it times out.
Signed-off-by: Grant Curell <[email protected]>
OME Version
3.8
Description
OME Does not correctly handle the @odata.nextLink attribute for /api/DeviceService/Devices when passed specific IDs. For example:
The first page of 50 results works as expected. However, after retrieval of the first set of 50 machines the nextLink url is truncated to '/api/DeviceService/Devices?$skip=50&$top=50' instead of properly including the IDs listed in the original URL. This leads to automated code looping over the totality of the OME inventory instead of some list of specified IDs.
The text was updated successfully, but these errors were encountered: