Provide successResponse body for EventLog Entries
This change ensures that success response body is provided when deleting
EventLog entries.
Status Code 204 No Content causes user confusion when using things
like curl. Follow other deletes.
redfish/v1/Systems/system/LogServices/EventLog/Actions/\
LogService.ClearLog -w "%{http_code}\n"
{
"@Message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_1_1.Message",
"Message": "The request completed successfully.",
"MessageArgs": [],
"MessageId": "Base.1.19.Success",
"MessageSeverity": "OK",
"Resolution": "None."
}
]
}
Change-Id: I443fdbb29e041a515dd3ee793cc73f27096ab23e
Signed-off-by: Sandeep Patil <sandeepap@ami.com>
diff --git a/redfish-core/lib/log_services.hpp b/redfish-core/lib/log_services.hpp
index adb12c1..6b8d075 100644
--- a/redfish-core/lib/log_services.hpp
+++ b/redfish-core/lib/log_services.hpp
@@ -1366,7 +1366,7 @@
return;
}
- asyncResp->res.result(boost::beast::http::status::ok);
+ messages::success(asyncResp->res);
};
// Make call to Logging service to request Delete Log