display device reported status and drive config - #371
saimonation wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 935ce59. Configure here.
| 'deviceReportedStatus.storage.status.summary.state', | ||
| 'deviceReportedStatus.storage.status.summary.totalDriveCount', | ||
| 'deviceReportedStatus.storage.status.summary.totalVolumeCount', | ||
| 'deviceReportedStatus.storage.status.summary.unusedDriveCount', |
There was a problem hiding this comment.
Wrong device reported storage path
High Severity
The new deviceReportedStatus.storage.status.summary.* selectors invert status and storage relative to the device API and to the existing metadata.status.storage.summary.* and deviceReportedStatus.status.device.* paths. filter_object will not find these fields, so portal-reported drive summary data is omitted from the export.
Reviewed by Cursor Bugbot for commit 935ce59. Configure here.


Note
Low Risk
Export field remapping and an extra read-only API include during device inspection; no auth or write-path changes.
Overview
Device export now pulls volume and drive summary metrics from
deviceReportedStatus(underproc.storage.summaryandstorage.status.summary) instead of top-levelproc.storage/storage.statuspaths on each portal device.Connected-device inspection also requests
/status/storagealongside existing config resources so reported storage status is available inmetadatafor the same export filter paths that already usemetadata.status.storage.*.Reviewed by Cursor Bugbot for commit 935ce59. Configure here.