tree 3721b985e2236a1e8c5bd44dbe77f7ff72fa9a01
parent 2aacf85668ebb4653e8e16d01c2ed2245a92c2fa
author Ed Tanous <edtanous@google.com> 1653505251 -0700
committer Ed Tanous <edtanous@google.com> 1655479979 -0700

Move the JsonSchemas to be generated at runtime

Generating all of these index files at compile time is kind of wasteful,
considering that it's really not that much code to generate them.  This
commit modifies the update_schemas script to generate a C++ version of
the schemas that can then be used to generate a route.  This allows
deleting a LOT of fixed files, for a very small incremental binary size
increase.

This change will cause two impacts that a user could possibly notice.

Expand will now work properly on JsonSchemas tree.
Keys on the JsonSchema schemas will now be sorted alphabetically, as we
do elsewhere.

All other things should remain the same.

Tested:
Redfish service validator passes.

curl --insecure --user root:0penBmc https://192.168.7.2/redfish/v1/JsonSchemas/Triggers
Returns the same object as before with changes above.

This adds 2512 bytes to the bmcweb binary size, and interestingly, adds
3764 bytes to the overall rootfs size, despite the level of file
     deletion seen in the patch.  While this is debatably "worse" than
     what we had before in this regard, making JsonSchemas work similar
     to how the rest of the Redfish tree operates, is worth the minor
     increase in code size.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ic0d568112a3784821aa6867f7bcf50705dc586db