This patch makes runValidation use startWorkflow wrapper to properly
handle it's execution. This change makes handling validations much
simpler as there is no specific onFinished callback needed as validations
only operate on incoming workflow executions which is handled by
WorkflowActions by default.
To properly distinguish between start validation and finished validation
messages (which use the same type) additional logic to zaqar action
was added.
runValidationGroups action remains the same as we handle validations
individually
Reviewed: https:/ /review. openstack. org/550086 /git.openstack. org/cgit/ openstack/ tripleo- ui/commit/ ?id=6e55c9f0a54 9e533a5e470120f 58c78b73dc70b0
Committed: https:/
Submitter: Zuul
Branch: master
commit 6e55c9f0a549e53 3a5e470120f58c7 8b73dc70b0
Author: Jiri Tomasek <email address hidden>
Date: Tue Mar 6 14:55:38 2018 +0100
Make Validation actions use startWorkflow
This patch makes runValidation use startWorkflow wrapper to properly
handle it's execution. This change makes handling validations much
simpler as there is no specific onFinished callback needed as validations
only operate on incoming workflow executions which is handled by
WorkflowActions by default.
To properly distinguish between start validation and finished validation
messages (which use the same type) additional logic to zaqar action
was added.
runValidati onGroups action remains the same as we handle validations
individually
Partial-Bug: #1753474 b87fe7ed672548b c9c59865ae0
Change-Id: Ie0f2f1c5175ca8