|
Post by elijahliang on Oct 22, 2020 8:48:06 GMT
Hi All, For the current latest Redfish schema bundle, DSP8010_2020.3, the readonly annotation is missing from the following properties. - AccountService.v1_7_2.json
ExternalAccountProvider.RemoteRoleMapping
- ComputerSystem.v1_9_4.json
TrustedModules
- Connection.v1_0_0.json
VolumeInfo
- Drive.v1_9_2.json
Identifiers Location Operations
- ... Omit other schemas ...
However, all other array properties have readonly annotation. Do all array properties need to have readonly annotation? And if not, what is the reason? With Regards, ElijahLiang
|
|
|
Post by mraineri on Oct 23, 2020 14:23:23 GMT
When it comes to objects and arrays of objects, putting the permission at the object-level has caused confusion. Marking it as read-only or read-write might imply to some that the entire object is read-only or read-write. In the majority of cases, this is never true; in some objects there are a subset of properties that are writable, and others are read-only. So, the pattern we use is we only mark the lowest order properties (numbers, strings, booleans) with permissions, and never mark the permissions at the object-level.
|
|