Custom Query should always use vserver 25/102425/2
authorJim Hahn <jrh3@att.com>
Wed, 26 Feb 2020 16:07:35 +0000 (11:07 -0500)
committerJim Hahn <jrh3@att.com>
Wed, 26 Feb 2020 16:17:18 +0000 (11:17 -0500)
commit72b4a13723049c5d4a066879aa67d08ec5e86180
treeef98a84a5b0a4e0bda8ab88016271f380b5ab592
parentaa2e18733fbaa2a0910091eca9677c076c53f454
Custom Query should always use vserver

Modified the Custom Query Operation to ignore the target entity
passed via the "params" and always use the vserver name found in
the enrichment data.

Issue-ID: POLICY-2349
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: If2c45df2d0377ca08059bdbfa0bcc3d3f043c5b9
models-interactions/model-actors/actor.aai/src/main/java/org/onap/policy/controlloop/actor/aai/AaiCustomQueryOperation.java
models-interactions/model-actors/actor.aai/src/test/java/org/onap/policy/controlloop/actor/aai/AaiCustomQueryOperationTest.java