Use the standard messaging in the validations workbook
Update the validations workbook to use the standard message sending
workflow. This workflow reduces the boilerplate that is copied between
workflows by defining the message structure, providing the retry logic
and ensuring the task on a "FAILED" message.
The workflow also offers optional persistence in Swift. If the plan name
is given to the workflow it will store the messages in a Swift container
named <plan_name>-messages.
Reviewed: https:/ /review. openstack. org/572340 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=34b4d10634c d56413f610cd8c4 e0c19baf04f28b
Committed: https:/
Submitter: Zuul
Branch: master
commit 34b4d10634cd564 13f610cd8c4e0c1 9baf04f28b
Author: Dougal Matthews <email address hidden>
Date: Tue Jun 5 12:06:27 2018 +0100
Use the standard messaging in the validations workbook
Update the validations workbook to use the standard message sending
workflow. This workflow reduces the boilerplate that is copied between
workflows by defining the message structure, providing the retry logic
and ensuring the task on a "FAILED" message.
The workflow also offers optional persistence in Swift. If the plan name -messages.
is given to the workflow it will store the messages in a Swift container
named <plan_name>
Change-Id: I162407a561cae4 e8e7fd665ccbb45 9b6ccf00bf4
Related-Bug: #1757372