diff options
| author | Ed Tanous <ed@tanous.net> | 2020-09-28 17:59:52 +0300 |
|---|---|---|
| committer | Ed Tanous <ed@tanous.net> | 2023-07-06 19:58:28 +0300 |
| commit | 24d67ff8960f210b574738f53b44a73ebdd4c003 (patch) | |
| tree | 43a0d65a6dc0f9e81381618360de3bfd782b7a64 /include/ibm | |
| parent | e002dbc0f8319bca613c38a683a856bde91dfdaf (diff) | |
| download | bmcweb-24d67ff8960f210b574738f53b44a73ebdd4c003.tar.xz | |
Remove IBM console events from Redfish
The /ibm/v1 console is a different tree than Redfish, and as such,
should not be sending non-redfish resource events out. This is very
likely to break redfish clients on the other end. If the management
console wants an event-like entity, it needs to come up with its own
EventService-like resource, considering it is a separate tree.
Significant related discussion occurred here:
https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/36368
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: Ic2a9e572099490f8810e03ab08336518f5672690
Diffstat (limited to 'include/ibm')
| -rw-r--r-- | include/ibm/management_console_rest.hpp | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/include/ibm/management_console_rest.hpp b/include/ibm/management_console_rest.hpp index edf64a4324..579d46c431 100644 --- a/include/ibm/management_console_rest.hpp +++ b/include/ibm/management_console_rest.hpp @@ -219,17 +219,11 @@ inline void handleFilePut(const crow::Request& req, { BMCWEB_LOG_DEBUG << "config file is updated"; asyncResp->res.jsonValue["Description"] = "File Updated"; - - redfish::EventServiceManager::getInstance().sendEvent( - redfish::messages::resourceChanged(), origin, "IBMConfigFile"); } else { BMCWEB_LOG_DEBUG << "config file is created"; asyncResp->res.jsonValue["Description"] = "File Created"; - - redfish::EventServiceManager::getInstance().sendEvent( - redfish::messages::resourceCreated(), origin, "IBMConfigFile"); } } @@ -383,7 +377,6 @@ inline void asyncResp->res.result(boost::beast::http::status::bad_request); return; } - redfish::EventServiceManager::getInstance().sendBroadcastMsg(broadcastMsg); } inline void handleFileUrl(const crow::Request& req, |