summaryrefslogtreecommitdiff
path: root/static/redfish/v1/schema/TriggersCollection_v1.xml
diff options
context:
space:
mode:
authorEd Tanous <edtanous@google.com>2022-09-23 22:03:18 +0300
committerEd Tanous <ed@tanous.net>2022-09-28 19:37:11 +0300
commit8b564558bafdf3e7a3babaafc29b0e5f904f4363 (patch)
treea003c08212abadfd82b218c0d22c28ca760646e0 /static/redfish/v1/schema/TriggersCollection_v1.xml
parent49aa131f718000ddd5fce833487f72b14990aa04 (diff)
downloadbmcweb-8b564558bafdf3e7a3babaafc29b0e5f904f4363.tar.xz
Sort schema list alphabetically
New versions of the DMTF schema pack seem to make this list parse in less-than-ideal order. Previously, the schema pack zip file had an order that was at least semi-alphabetical, but 2022.2 seems to cause that to change. This commit makes the update_schemas.py script explicitly alphabetize the list. This changes the order of two keys that have common prefixes, but leaves the rest of the order the same. Both are arguably correct. This commit also exposes that this script seemed to have lots of problems in its version number detection logic. To make all this work properly, a fairly invasive change is required. Tested: Running the script on 2021.4 produces the same result as previously. See later commits for 2022.2 where result is now correct. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Ia2365daee1d91de142652161bf752600f3109115
Diffstat (limited to 'static/redfish/v1/schema/TriggersCollection_v1.xml')
0 files changed, 0 insertions, 0 deletions