|
Post by AMI_Mani on Mar 23, 2020 15:47:23 GMT
Hi,
As per Storage.v1_8_0.json, MemberId is mentioned as string till Redfish v1.6, but Redfish v1.6 or higher suggest to zero-based array index. But in Redfish 1.5, we used string value as sata_controller_0, but as per schema we need change to zero-based array index in Redfish v1.6 or higher Can we expect type can be changed to number instead of string in schema? If it's going to be string type can we use sata_controller_0(unique value)? If we use string value sata_controller_0, redfish conformance tool is throwing error to use zero-based array index
"MemberId": { "description": "The identifier for the member within the collection.", "longDescription": "This property shall uniquely identify the member within the collection. For services supporting Redfish v1.6 or higher, this value shall contain the zero-based array index.", "readonly": true, "type": "string" }
Thanks, Mani
|
|
|
Post by jautor on Mar 23, 2020 21:39:23 GMT
No, the identification values are still strings (both `Id` and `MemberId` follow this pattern), even though in the case of `MemberId` it will always be a numeric value. It is still represented as a string - there no change to the schema definition (still a "string" type).
So:
"MemberId": "2", <---- CORRECT
But not:
"Memberid": 2, <---- INCORRECT
And going forward, the `MemberId` must be the zero-based array index value. They were always supposed to follow that pattern, but this was missed in the schema descriptions and was corrected when the Specification v1.6 was under review.
Jeff
|
|
|
Post by AMI_Mani on Apr 1, 2020 11:15:33 GMT
Thanks Jeff for the details
Mani
|
|