Post by ueliyahu on Feb 20, 2023 15:21:40 GMT
In order to initialized UEFI bios attribute , one of the requirements from the UEFI team was to support PUT request to /redfish/v1/Registries/BiosAttributeRegistry/BiosAttributeRegistry.
Does PUT is valid request in this case ? I did not find an answer for that in DMFT documentation
Get request for /redfish/v1/Registries/BiosAttributeRegistry/BiosAttributeRegistry retrieve the following information
"Description": "This registry represent DPU's BIOS Attribute instances",
"Name": "DPU Bios Attribute Registry",
according to redfish.dmtf.org/schemas/v1/AttributeRegistry.v1_3_2.json it seems that PUT request can be supported
according to redfish.dmtf.org/schemas/v1/AttributeRegistry.json only GET request can be supported.
Post by Abner Chang on Feb 21, 2023 1:28:07 GMT
, We don't allow users to write to BIOS AttributeRegistry because AttributeRegistry is used to represent the BIOS Attribute characteristics and the attributes hierarchy from UI viewpoint. If you were saying BIOS->BMC when provisioning the BIOS AttributeRegistry through PUT, the Host Interface boot credential can give different privileges to BIOS as it is a provider. However, this would be the agreement between BIOS and BMC, not the Redfish spec or defined in the schema.