Fix operation history DB properties for Junits 37/19137/3
authorTemoc Rodriguez <cr056n@att.com>
Mon, 16 Oct 2017 20:37:05 +0000 (13:37 -0700)
committerTemoc Rodriguez <cr056n@att.com>
Tue, 17 Oct 2017 19:44:36 +0000 (12:44 -0700)
commitb715f669284012b1d25c183e73b550c4648abd1a
tree35ad4ae4968c70848d70b071ec5577059ab44174
parentd5066ba5c2d15bcc9bf00b9a52a1ce54a43449af
Fix operation history DB properties for Junits

Removed operation_history.properties / operations-history.properties.
Changed the properties in persistence.xml
so that it uses the correct values. Previously junit would never write
to db because the "guard.disabled" property was not set. Set this property.
Additionally the operationshistory10 table was trying to be created even
though it exists. These values work in junit code. Not tested on
rackspace yet.

Issue-ID: POLICY-345
Change-Id: Id755b3152ae6ac4991ea9c314154592ea0105070
Signed-off-by: Temoc Rodriguez <cr056n@att.com>
controlloop/common/eventmanager/src/main/java/org/onap/policy/controlloop/eventmanager/ControlLoopOperationManager.java
controlloop/common/eventmanager/src/main/resources/META-INF/persistence.xml
controlloop/common/guard/src/main/java/org/onap/policy/guard/PIPEngineGetHistory.java
controlloop/common/guard/src/main/java/org/onap/policy/guard/Util.java
controlloop/common/guard/src/main/resources/operation_history.properties [deleted file]
controlloop/templates/template.demo/src/test/java/org/onap/policy/template/demo/Util.java