Use the standard messaging in the derive_parameters workbook
Update the derive_parameters 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/554548 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=53b1704d990 900b504b6f24742 ce8cc95d39a3ed
Committed: https:/
Submitter: Zuul
Branch: master
commit 53b1704d990900b 504b6f24742ce8c c95d39a3ed
Author: Dougal Matthews <email address hidden>
Date: Tue Mar 20 13:54:19 2018 +0000
Use the standard messaging in the derive_parameters workbook
Update the derive_parameters 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>
Related-Bug: #1757372 041754522d30cb1 a110ea7186d
Change-Id: If9bcf6f0348d06