tree 350ed0f217777f6a91c08de386d695b0d7ba311d
parent 9017faf2918308a375f37bebc9d431da9a75a7b2
author Carson Labrado <clabrado@google.com> 1657313812 +0000
committer Ed Tanous <ed@tanous.net> 1673140344 +0000

Aggregation: Generate collections from schema

In aggregation we need to account for when a satellite BMC supports a
resource collection that the aggregating BMC does not.  We need to
add links in responses from upstream resources to indicate that these
satellite only resources exist.  These top level collections do not
always have the location format of /redfish/v1/<collection_id>.  We
determine all of those from the schema rather than hardcoding a few
choice exceptions that do not fit that format such as
/redfish/v1/UpdateService/FirmwareInventory.

This patch is the first step in accomplishing this.  We parse all
xml schema files in order to determine what are the top level
collection URIs.  For URIs that are upstream from top level collections
we'll be able to derive what URIs could appear in the response which
are also on the same path to a top level collection.

The xml files for resources that aren't currently supported by bmcweb
are ignored when creating the schema index and later deleted once the
above parsing completes.

Later patches will use this information to make sure that we are
properly handling all schema defined top level collections.

Tested:
Compiles with aggregation enabled

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