Add non-cloudowner nbrequest lookup in workflowAction 53/89553/2
authorMarcus G K Williams <marcus.williams@intel.com>
Fri, 7 Jun 2019 01:12:52 +0000 (18:12 -0700)
committerMarcus Williams <marcus.williams@intel.com>
Fri, 7 Jun 2019 00:36:52 +0000 (00:36 +0000)
Using a cloudOwner different than "CloudOwner"
when instantiating a vfmodule using GR_API
causes nbrequest lookup in workflowAction to
fail. This change adds a final check for
northboundRequest that does not use
cloudOwner field before failing.

This should enable instantiation
on multiple cloudRegions without
seperate northbound_request_ref_lookup
actions for each cloudOwner.

Issue-ID: SO-1995
Change-Id: I9d1fe39fb056d03e8473a524c21f41319c13c20f
Signed-off-by: Marcus G K Williams <marcus.williams@intel.com>
bpmn/so-bpmn-tasks/src/main/java/org/onap/so/bpmn/infrastructure/workflow/tasks/WorkflowAction.java

index 70726f2..7065c2c 100644 (file)
@@ -1323,6 +1323,10 @@ public class WorkflowAction {
             northBoundRequest = catalogDbClient.getNorthBoundRequestByActionAndIsALaCarteAndRequestScopeAndCloudOwner(
                     requestAction, resourceName.toString(), aLaCarte, cloudOwner);
         }
+        if (northBoundRequest == null) {
+            northBoundRequest = catalogDbClient.getNorthBoundRequestByActionAndIsALaCarteAndRequestScope(requestAction,
+                    resourceName.toString(), aLaCarte);
+        }
         if (northBoundRequest == null) {
             if (aLaCarte) {
                 buildAndThrowException(execution,