Use the standard messaging in the plan_management workbook
Update the plan_management 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.
This is a continuation of I9755eaa6621ec1d83fe98e20445a4f13b4ea0686.
Some old-style messaging was added after the refactor and some redundant
lines were not removed.
Reviewed: https:/ /review. openstack. org/576182 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=e47bbf649eb 7a888dd643af8d1 46f81d3bf21838
Committed: https:/
Submitter: Zuul
Branch: master
commit e47bbf649eb7a88 8dd643af8d146f8 1d3bf21838
Author: Dougal Matthews <email address hidden>
Date: Mon Jun 18 16:44:09 2018 +0100
Use the standard messaging in the plan_management workbook
Update the plan_management 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>
This is a continuation of I9755eaa6621ec1 d83fe98e20445a4 f13b4ea0686.
Some old-style messaging was added after the refactor and some redundant
lines were not removed.
Change-Id: Ia50e4055e24d07 cb39d4c05745bd6 694e94621f9
Related-Bug: #1757372