Return errormessages in failing imperative workflows 33/128533/1
authorJozsef Csongvai <jozsef.csongvai@bell.ca>
Tue, 12 Apr 2022 23:24:37 +0000 (19:24 -0400)
committerJozsef Csongvai <jozsef.csongvai@bell.ca>
Tue, 12 Apr 2022 23:31:23 +0000 (19:31 -0400)
commit577316e6c8fbf21bb25f41174cd80f7bd8df327a
tree8977e5e1877bf8bac713a35e6926a5e66e2deb0c
parent795c2d4349e04c4f7c0d4d5fb467727b8118b44a
Return errormessages in failing imperative workflows

Instead of discarding error messages after each node has executed, they
are now kept until the workflow completes. If the workflow completes
without exceptions, it means that all errors were handled and the error
messages can be cleared. If the workflow does complete with exceptions,
all error messages will be propagated in the response.

Also update UatExecutor to enable expected status codes other than 200.

Issue-ID: CCSDK-3630
Signed-off-by: Jozsef Csongvai <jozsef.csongvai@bell.ca>
Change-Id: I94fd81c342ad2a798e64051c603beb62bf1aaacd
components/model-catalog/blueprint-model/uat-blueprints/imperative_workflow/Definitions/uat-imperative-workflow.json
components/model-catalog/blueprint-model/uat-blueprints/imperative_workflow/Tests/uat.yaml
ms/blueprintsprocessor/application/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/uat/utils/UatExecutor.kt
ms/blueprintsprocessor/modules/blueprints/blueprint-core/src/main/kotlin/org/onap/ccsdk/cds/controllerblueprints/core/BluePrintError.kt
ms/blueprintsprocessor/modules/services/workflow-service/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/services/workflow/ImperativeWorkflowExecutionService.kt