Create dynamic data-type using all workflow steps 81/130781/1
authorJozsef Csongvai <jozsef.csongvai@bell.ca>
Tue, 6 Sep 2022 23:05:02 +0000 (19:05 -0400)
committerJozsef Csongvai <jozsef.csongvai@bell.ca>
Wed, 7 Sep 2022 13:35:49 +0000 (09:35 -0400)
commit27778ac1289588a9f68e9b9408819f7bfb1c7d21
tree57ae232cde08ae090f0808ff9f524c2b53ae62e2
parent4899f6bd4e00fa20bd0cac4a60c04a959b8e88c7
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
ms/blueprintsprocessor/modules/inbounds/designer-api/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/designer/api/enhancer/BluePrintWorkflowEnhancerImpl.kt