control: `member` signal triggers use event groups
Remove the ability to provide a `member` trigger's attributes from the
event trigger configuration in favor of using the configured event's
groups. This aligns with the recent design direction that event triggers
are setup from the event groups.
Change-Id: I304cfdffedd54317e440e7566988392a1410af6a
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
diff --git a/control/json/triggers/signal.hpp b/control/json/triggers/signal.hpp
index 881673a..6db4dbb 100644
--- a/control/json/triggers/signal.hpp
+++ b/control/json/triggers/signal.hpp
@@ -89,10 +89,9 @@
* @param[in] mgr - Pointer to manager of the trigger
* @param[in] group - Group to subscribe signal against
* @param[in] actions - Actions to be run when signal is received
- * @param[in] jsonObj - JSON object for the trigger
*/
-void member(Manager* mgr, const Group&, SignalActions actions,
- const json& jsonObj);
+void member(Manager* mgr, const Group& group, SignalActions actions,
+ const json&);
// Match setup function for signals
using SignalMatch = std::function<void(Manager*, const Group&,