Allow guards to be dynamically enabled/disabled 25/111925/1
authorJim Hahn <jrh3@att.com>
Mon, 31 Aug 2020 21:59:44 +0000 (17:59 -0400)
committerJim Hahn <jrh3@att.com>
Mon, 31 Aug 2020 22:04:27 +0000 (18:04 -0400)
commit25c8a555a739b1c80966ed88cc123a6e9ad9318e
treed165abf12e68cf51219bcb2f3ff128cdf36a0570
parent1c5cb8a0d740ccd92d2b3fdce8eb192cd20b147f
Allow guards to be dynamically enabled/disabled

Modified drools-apps so that guards can be dynamically enabled and
disabled.  Due to the current design, there are two properties that
control this:
- an actor-level property: when enabled, the DB connection is created,
  otherwise a stub connection is created.  This property is NOT dynamic
- an engine-level property: when enabled, the connection created by the
  actor is used, otherwise a stub connection is used.  This property IS
  dynamic

Issue-ID: POLICY-2748
Change-Id: I2a5baf908ce274f2eb46a6a3f01df1b3532038ff
Signed-off-by: Jim Hahn <jrh3@att.com>
controlloop/common/controller-usecases/src/main/resources/usecases.drl
controlloop/common/eventmanager/src/main/java/org/onap/policy/controlloop/eventmanager/ControlLoopEventManager.java
controlloop/common/eventmanager/src/test/java/org/onap/policy/controlloop/eventmanager/ControlLoopEventManagerTest.java