Add fix for guard db on disable 89/17389/2
authorTemoc Rodriguez <cr056n@att.com>
Fri, 6 Oct 2017 14:57:02 +0000 (07:57 -0700)
committerTemoc Rodriguez <cr056n@att.com>
Fri, 6 Oct 2017 14:57:02 +0000 (07:57 -0700)
commit5a8dcfc830a71d28029254a14aa9a085b9a8af5a
tree36287ac1223171f2098d00e0931a2ae8ff346447
parentdb6d2468fc672a23ed152b8624b34de01ff13233
Add fix for guard db on disable

Added a fix so that the guard database is not attempted to be accessed
while guard is set to disabled. The guard db access is done in the
operations manager which has no context of guardat the moment. Because
of this separation, the boolean must be grabbed from the PolicyEngine
properties. We should consider some guard refactoring.

Issue-ID: POLICY-296
Change-Id: Ida7a2a7c19e568b076731e0f04bdc8a9fd0fcb26
Signed-off-by: Temoc Rodriguez <cr056n@att.com>
controlloop/common/eventmanager/src/main/java/org/onap/policy/controlloop/eventmanager/ControlLoopOperationManager.java