Pull in all registries

Before Redfish put all messages in Base, but as the Messages became more
specific Redfish started creating new registries. Redfish might have
went a little registry happy. HeartbeatEvent just has 1 message and all
these new ones registries each just have a handful of messages.

Add the remaining 15 registries:
composition, environmental, ethernetfabric, fabric, heartbeat_event,
job_event, license, logservice, networkdevice, platform, power,
sensor_event, storage_device, telemetry, update.

Some of these are wanted for both current development and future
development but it is hard to decide which ones so just added them all.
power, fabric, telemetry, update are all things we support today. Having
a UpdateInProgress or UpdateSuccessful makes a lot of sense and this
enables that.

Put these alphabetically. Use a new for loop to do this.

Make changes to scripts/parse_registries.py and run the tool.

No difference in size.

Before: 66928640 Apr 10 13:32
obmc-phosphor-image-p10bmc-20240410183051.ext4.mmc.tar

After: 66928640 Apr 10 13:18
obmc-phosphor-image-p10bmc-20240410181439.ext4.mmc.tar

Tested: bmcweb builds.
"./scripts/parse_registries.py --registries license,update" works.

Change-Id: I43b4d041531cf338e9e7e621714ca7d95f6b01a5
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>

1 files changed, 55 insertions, 0 deletions

diff --git a/redfish-core/include/registries/log_service_message_registry.hpp b/redfish-core/include/registries/log_service_message_registry.hpp
new file mode 100644
index 0000000000..b855323cf4
--- /dev/null
+++ b/redfish-core/include/registries/log_service_message_registry.hpp
@@ -0,0 +1,55 @@
+#pragma once
+/****************************************************************
+ *                 READ THIS WARNING FIRST
+ * This is an auto-generated header which contains definitions
+ * for Redfish DMTF defined messages.
+ * DO NOT modify this registry outside of running the
+ * parse_registries.py script.  The definitions contained within
+ * this file are owned by DMTF.  Any modifications to these files
+ * should be first pushed to the relevant registry in the DMTF
+ * github organization.
+ ***************************************************************/
+#include "registries.hpp"
+
+#include <array>
+
+// clang-format off
+
+namespace redfish::registries::log_service
+{
+const Header header = {
+    "Copyright 2020-2023 DMTF. All rights reserved.",
+    "#MessageRegistry.v1_6_2.MessageRegistry",
+    "LogService.1.0.1",
+    "Log Service Message Registry",
+    "en",
+    "This registry defines the messages for log service related events.",
+    "LogService",
+    "1.0.1",
+    "DMTF",
+};
+constexpr const char* url =
+    "https://redfish.dmtf.org/registries/LogService.1.0.1.json";
+
+constexpr std::array registry =
+{
+    MessageEntry{
+        "DiagnosticDataCollected",
+        {
+            "Indicates that diagnostic data was collected due to a client invoking the `CollectDiagnosticData` action.",
+            "'%1' diagnostic data collected.",
+            "OK",
+            1,
+            {
+                "string",
+            },
+            "None.",
+        }},
+
+};
+
+enum class Index
+{
+    diagnosticDataCollected = 0,
+};
+} // namespace redfish::registries::log_service