BMC/OpenBmc/bmcweb.git/redfish-core/include/generated/enums/manager.hpp, branch master

Move to Redfish 2026.1

2026-05-19T19:16:28+00:00

One line change and rerun the script. 2026.1 includes new properties. The overview is at [1]. [1]: https://www.dmtf.org/sites/default/files/Redfish_Release_2026.1_Overview.pdf Tested: Inspection only. Change-Id: I007f074128e278fb267ee4de3b9cbab22d6336df Signed-off-by: Gunnar Mills

Move clang-off / clang-on to catch scope

2026-01-26T20:35:54+00:00

As a comment in https://gerrit.openbmc.org/c/openbmc/bmcweb/+/86868 suggested "You might also consider moving this up a line so you catch the scope on both sides." This enforces just the slightest bit more clang-format. Rerun script. Tested: Builds. Manual changes to script only. Rest generated. Change-Id: I8ff01befc56c576716f5d83bd90763354b1ff0c5 Signed-off-by: Gunnar Mills

Modify enum generation for clang

2026-01-23T14:50:11+00:00

Clang-format was unhappy with the new redfish-core/include/generated/enums/switch.hpp in 2025.4 ``` diff --git a/redfish-core/include/generated/enums/switch.hpp b/redfish-core/include/generated/enums/switch.hpp index 6acf6e28..cabc8562 100644 --- a/redfish-core/include/generated/enums/switch.hpp +++ b/redfish-core/include/generated/enums/switch.hpp @@ -5,7 +5,7 @@ namespace switch { -// clang-format off + // clang-format off ``` Move turning clang-format off before the namespace fixes. ¯\_(ツ)_/¯ Do that in generate_schema_enums.py and rerun update_schemas.py. Adding 4 spaces before the clang-format off broke other generated enums. Broke out from 2025.4. Tested: Visual and build only. Change-Id: Ic03aa558b405957f15035570d376c46c545906c0 Signed-off-by: Gunnar Mills

Update to 2025.2

2025-06-17T16:39:07+00:00

1 line change in update_schemas.py and rerun it. See below for more info on this release [1] Tested: Inspection only. These have not broke things in the past. [1]: https://www.dmtf.org/sites/default/files/Redfish_Release_2025.2_Overview.pdf Change-Id: I641bc4285fa502a5d81318ff56eaeb75c0af4762 Signed-off-by: Gunnar Mills

Update to 2025.1

2025-03-26T21:41:54+00:00

1 line change in update_schemas.py and rerun it. See below for more info on this release: https://www.dmtf.org/content/redfish-release-20251-now-available Tested: Inspection only. These have not broke things in the past. Change-Id: I8d386725b364e2bc7c91c869e519e5e7bfbf11f9 Signed-off-by: Gunnar Mills

Update to 2024.4

2025-01-22T19:04:24+00:00

Update schema to the latest release 2024.4. See below for more info on this release: https://www.dmtf.org/standards/redfish Tested: - Redfish Service Validator passes Change-Id: I1845d6afa04ee418ba3ab0bd0bc8ce59886e4376 Signed-off-by: Myung Bae

Use SPDX identifiers

2025-01-20T18:44:54+00:00

SPDX identifiers are simpler, and reduce the amount of cruft we have in code files. They are recommended by linux foundation, and therefore we should do as they allow. This patchset does not intend to modify any intent on any existing copyrights or licenses, only to standardize their inclusion. [1] https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects Change-Id: I935c7c0156caa78fc368c929cebd0f068031e830 Signed-off-by: Ed Tanous

Generate Redfish enums from schemas

2022-12-08T20:08:01+00:00

OpenBMC tends to have a significant problem in doing the appropriate lookups from the schema files, and many bugs have been injected by users picking a bad enum, or mistyping the casing of an enum value. At the same time, nlohmann::json has recently added first class support for enums, https://json.nlohmann.me/features/enum_conversion/ This commit attempts to build a set of redfish includes file with all the available Redfish enums in an easy to use enum class. This makes it very clear which enums are supported by the schemas we produce, and adds very little to no extra boilerplate on the human-written code we produced previously. Note, in the generated enum class, because of our use of the clang-tidy check for macros, the clang-tidy check needs an exception for these macros that don't technically follow the coding standard. This seems like a reasonable compromise, and in this case, given that nlohmann doesn't support a non-macro version of this. One question that arises is what this does to the binary size.... Under the current compiler optimizations, and with the current best practices, it leads to an overall increase in binary size of ~1200 bytes for the enum machinery, then approximately 200 bytes for every call site we switch over. We should decide if this nominal increase is reasonable. Tested: Redfish protocol validator runs with same number of failures as previously. Redfish Service Validator passes (one unrelated qemu-specific exception) Signed-off-by: Ed Tanous Change-Id: I7c7ee4db0823f7c57ecaa59620b280b53a46e2c1