Post by chaul on Aug 28, 2023 8:32:35 GMT
Hi, the IntrusionSensorRearm attribute under PhysicalSecurity is currently defined as read-only (https://redfish.dmtf.org/schemas/v1/Chassis.v1_23_0.json).
"IntrusionSensorReArm": {
"anyOf": [
{
"$ref": "#/definitions/IntrusionSensorReArm"
},
{
"type": "null"
}
],
"description": "The policy that describes how the physical security state of the chassis returns to a normal state.",
"longDescription": "This property shall contain the policy that describes how the IntrusionSensor property returns to the `Normal` value.",
"readonly": true,
"versionAdded": "v1_1_0"
}
I can see it means that the rearm method should be chosen from the beginning and can not be changed along the way. But I wonder what the drawback of allowing it to be writable is? I think admin should be allowed to change runtime how they interpret the IntrusionSensor value.
Thanks.
"IntrusionSensorReArm": {
"anyOf": [
{
"$ref": "#/definitions/IntrusionSensorReArm"
},
{
"type": "null"
}
],
"description": "The policy that describes how the physical security state of the chassis returns to a normal state.",
"longDescription": "This property shall contain the policy that describes how the IntrusionSensor property returns to the `Normal` value.",
"readonly": true,
"versionAdded": "v1_1_0"
}
I can see it means that the rearm method should be chosen from the beginning and can not be changed along the way. But I wonder what the drawback of allowing it to be writable is? I think admin should be allowed to change runtime how they interpret the IntrusionSensor value.
Thanks.
