Create dynamic data-type using all workflow steps 04/131204/1
authorJozsef Csongvai <jozsef.csongvai@bell.ca>
Tue, 6 Sep 2022 23:05:02 +0000 (19:05 -0400)
committerLukasz Rajewski <lukasz.rajewski@t-mobile.pl>
Fri, 30 Sep 2022 13:51:32 +0000 (13:51 +0000)
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
(cherry picked from commit 27778ac1289588a9f68e9b9408819f7bfb1c7d21)

ms/blueprintsprocessor/modules/inbounds/designer-api/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/designer/api/enhancer/BluePrintWorkflowEnhancerImpl.kt

index dd60aca..d7c2e07 100644 (file)
@@ -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)")