created AddReportFutureVersion dbus method
New method will support CollectionTimeScope, CollectionDuration
In order to make not breaking interface changes bmcweb will switch to
AddReportFutureVersion, then AddReport will be changed to match
AddReportFutureVersion, then redfish will switch back to use AddReport,
then AddReportFutureVersion will be removed.
Tested:
- Verified that current version of bmcweb works fine with old API
Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com>
Change-Id: I51a9b7fb2f4da5b8d2f688ccd5e93710352b1ac7
diff --git a/src/numeric_threshold.cpp b/src/numeric_threshold.cpp
index 5cc2be5..ebb7826 100644
--- a/src/numeric_threshold.cpp
+++ b/src/numeric_threshold.cpp
@@ -3,11 +3,10 @@
#include <phosphor-logging/log.hpp>
NumericThreshold::NumericThreshold(
- boost::asio::io_context& ioc,
- std::vector<std::shared_ptr<interfaces::Sensor>> sensorsIn,
+ boost::asio::io_context& ioc, Sensors sensorsIn,
std::vector<std::string> sensorNames,
std::vector<std::unique_ptr<interfaces::TriggerAction>> actionsIn,
- std::chrono::milliseconds dwellTimeIn, numeric::Direction direction,
+ Milliseconds dwellTimeIn, numeric::Direction direction,
double thresholdValueIn) :
ioc(ioc),
sensors(std::move(sensorsIn)), actions(std::move(actionsIn)),
@@ -72,7 +71,7 @@
uint64_t timestamp, double value, bool& dwell,
boost::asio::steady_timer& timer)
{
- if (dwellTime == std::chrono::milliseconds::zero())
+ if (dwellTime == Milliseconds::zero())
{
commit(sensorName, timestamp, value);
}