Create dynamic data-type using all workflow steps

Only the first step was used to create dynamic data-type in imperative
workflows. Unless the first step was targeting resource resolution
component, the dynamic data-type would not be created. This prevents
resolution of workflow input properties.

Issue-ID: CCSDK-3764
Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca>
Change-Id: Ic51808f2ee0d74d6c4b07565e0caf12adc3e2590

diff --git a/ms/blueprintsprocessor/modules/inbounds/designer-api/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/designer/api/enhancer/BluePrintWorkflowEnhancerImpl.kt b/ms/blueprintsprocessor/modules/inbounds/designer-api/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/designer/api/enhancer/BluePrintWorkflowEnhancerImpl.kt
index dd60aca..d7c2e07 100644 (file)
--- a/ms/blueprintsprocessor/modules/inbounds/designer-api/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/designer/api/enhancer/BluePrintWorkflowEnhancerImpl.kt
+++ b/ms/blueprintsprocessor/modules/inbounds/designer-api/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/designer/api/enhancer/BluePrintWorkflowEnhancerImpl.kt
@@ -129,7 +129,7 @@ open class BluePrintWorkflowEnhancerImpl(
             dependencyNodeTemplates =
                 JacksonUtils.getListFromJsonNode(dependencyNodeTemplateNodes, String::class.java)
         } else {
-            dependencyNodeTemplates = listOf(nodeTemplateName)
+            bluePrintContext.workflowByName(name).steps!!.map { it.value.target!! }.let { dependencyNodeTemplates = it }
         }
 
         log.info("workflow($name) dependent component NodeTemplates($dependencyNodeTemplates)")