Fix incorrect policy with time-in-range 61/85261/5
authorPamela Dragosh <pdragosh@research.att.com>
Sat, 13 Apr 2019 15:42:55 +0000 (11:42 -0400)
committerPamela Dragosh <pdragosh@research.att.com>
Mon, 15 Apr 2019 11:59:36 +0000 (07:59 -0400)
commitf0fd32d9eafb3252f31807b1c999ca949a2f5ad3
tree6b7b64f93145ae1bd36f4d198b4b20cb50db0e0b
parent70736cfbf6ad1a068f8ee53adddd4faa3b6fa8a8
Fix incorrect policy with time-in-range

Changed policies to use Z vs -05:00 for timezone since
we cannot guarantee the timezone the VM's run in. The
test should be generalized.

Fixed a sonar issue in the test I was using to debug this.

Issue-ID: POLICY-1639
Change-Id: If3e52d199527a8a7e11c5fa994beb8fb886c93a6
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
applications/guard/src/test/java/org/onap/policy/xacml/pdp/application/guard/GuardPdpApplicationTest.java
applications/guard/src/test/resources/vDNS.policy.guard.blacklist.output.tosca.yaml
applications/guard/src/test/resources/vDNS.policy.guard.frequency.output.tosca.yaml
applications/guard/src/test/resources/vDNS.policy.guard.minmax.output.tosca.yaml