Is this a new feature, an enhancement, or a change to existing functionality?
Enhancement
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
A captured BMC response may report ReactionDelaySeconds as 0.0, while the generated nv_redfish::LeakDetector model correctly requires an integer. Health does not use this property, but deserialization fails before the collector can process DetectorState and Status.State. Leak-detector health collection therefore fails for the complete response.
Feature Description
Deserialize leak-detector responses into a collector-local payload containing only the fields required for health reporting:
@odata.id@odata.etagDetectorStateStatus.StateUserLabel
Reuse nv-redfish types for these fields and keep the generated LeakDetector model unchanged. Continue rejecting invalid values in fields used by health.
Tradeoff
The local payload becomes the collector's explicit wire contract. A future change that consumes another Redfish property must add that property to the local payload and extend the collector tests. This maintenance is limited to fields that affect health behavior and avoids making unrelated generated properties runtime dependencies.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
Enhancement
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
A captured BMC response may report
ReactionDelaySecondsas0.0, while the generatednv_redfish::LeakDetectormodel correctly requires an integer.Healthdoes not use this property, but deserialization fails before the collector can processDetectorStateandStatus.State. Leak-detector health collection therefore fails for the complete response.Feature Description
Deserialize leak-detector responses into a collector-local payload containing only the fields required for health reporting:
@odata.id@odata.etagDetectorStateStatus.StateUserLabelReuse
nv-redfishtypes for these fields and keep the generatedLeakDetectormodel unchanged. Continue rejecting invalid values in fields used by health.Tradeoff
The local payload becomes the collector's explicit wire contract. A future change that consumes another Redfish property must add that property to the local payload and extend the collector tests. This maintenance is limited to fields that affect health behavior and avoids making unrelated generated properties runtime dependencies.
Describe your ideal solution
No response
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct