diff options
author | Ed Tanous <edtanous@google.com> | 2022-02-08 11:41:53 +0300 |
---|---|---|
committer | Ed Tanous <ed@tanous.net> | 2022-03-08 02:10:00 +0300 |
commit | 5f2b84ee090bb9d361de9c294aa85cecf3962c11 (patch) | |
tree | 09c93476f94daa3f7e8cc599b0eca3cd4350c9ac /redfish-core/include/event_service_manager.hpp | |
parent | fffb8c1fae42bc5ed3b07a700b71fdaf7b59eab8 (diff) | |
download | bmcweb-5f2b84ee090bb9d361de9c294aa85cecf3962c11.tar.xz |
Drop message severity
In the way we store the message registry, we store both Severity and
MessageSeverity. Severity as a field is deprecated, and in every case
in every registry both fields have the same value. We shouldn't
duplicate data in that way. This commit changes the parse_registries.py
script to stop producing the Severity field into the struct. The few
uses we have left are moved over to use MessageRegistry.
Tested:
Redfish service validator shows no errors on the
/redfish/v1/Registries tree. Other errors present that were there
previously and are unchanged.
This saves a trivial amount: about 1kB on our compressed binary size.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ibbaf533dc59eb08365d6ed309aba16b54bc40ca1
Diffstat (limited to 'redfish-core/include/event_service_manager.hpp')
-rw-r--r-- | redfish-core/include/event_service_manager.hpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/redfish-core/include/event_service_manager.hpp b/redfish-core/include/event_service_manager.hpp index 0892df9b74..6cb95c4c5c 100644 --- a/redfish-core/include/event_service_manager.hpp +++ b/redfish-core/include/event_service_manager.hpp @@ -236,7 +236,7 @@ inline int formatEventLogEntry(const std::string& logEntryID, if (message != nullptr) { msg = message->message; - severity = message->severity; + severity = message->messageSeverity; } redfish::registries::fillMessageArgs(messageArgs, msg); |