Aggregation: Ignore JsonSchemas and fix prefixes

We don't want to aggregate JsonSchemas as-is since it can introduce
problems related to inconsistent versions between the aggregating and
satellite BMCs.  For now we will just assume that the aggregating BMC
will match all satellite BMCs in terms of schemas and versions.

There was also an edge case where we are not adding prefixes to "Uri"
keys.  These are used by Registries resources.  Now we make a case-
insensitive check to see if a key ends with "uri" in order to
determine if we need to add the prefix to the resource ID.

Tested:
Requests to /redfish/v1/JsonSchemas only show schemas on the
aggregating BMC.

Responses from /redfish/v1/Registries/<id> now contain the
aggregation prefix in the value associated with the "Uri" key.
~# curl localhost/redfish/v1/Registries/5B247A_TaskEvent
{
  ...
  "Location": [
    {
      ...
      "Uri": "/redfish/v1/Registries/5B247A_TaskEvent/TaskEvent"
    }
  ],
  ...
}

Signed-off-by: Carson Labrado <clabrado@google.com>
Change-Id: I935785740c05ad0ac3e8c682a72ae1d1419054a8

0 files changed, 0 insertions, 0 deletions