tree 81e6f129961c8e7444989a4819c3c2dfd1b4e68a
parent 8f9ee3cd141a0d49f703d4358c81ddb644703cc2
author Gunnar Mills <gmills@us.ibm.com> 1604087889 -0500
committer Gunnar Mills <gmills@us.ibm.com> 1604962567 +0000

AssetTag: Add PATCH support

Use the same AssetTag logic from the GET.
Look for xyz.openbmc_project.Inventory.Item.System interface then
call that service and path to set the AssetTag.

This assumes there is 1 "Item.System".
Considered something like
"if (!boost::ends_with(path, "system"))
continue;
"
but no where else does bmcweb check that the Item.System is named
"system" i.e. that /redfish/v1/Systems/system is actually named
"system" on D-Bus.

Considered looking that the service had the interface if not move
to the next service but the GET code does not so just followed it.

Tested:
 curl -k-X PATCH -d  '{"AssetTag": "Paramo"}'  https://${bmc}/redfish/v1/Systems/system/
 curl -k  https://${bmc}/redfish/v1/Systems/system/
{
  "@odata.id": "/redfish/v1/Systems/system",
  "@odata.type": "#ComputerSystem.v1_12_0.ComputerSystem",
  "Actions": {
    "#ComputerSystem.Reset": {
      "@Redfish.ActionInfo": "/redfish/v1/Systems/system/ResetActionInfo",
      "target": "/redfish/v1/Systems/system/Actions/ComputerSystem.Reset"
    }
  },
  "AssetTag": "Paramo",
 ...
Validator passes.

Change-Id: I45f80a8a69457f76e6e83ad2333856abe61de933
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>