Stop sending execution object via Zaqar message
Execution object can be quite large which is not suitable
for sending via Zaqar messages. Instead we're sending
execution_id and root_execution_id which can be used by the client
to retrieve execution details
Depends-On: Ia6c954e688589f69a7463f1b8e02244d029e8b7a
Change-Id: I010ea5d732aba97a554e868f62a19e6fdaee8889
(cherry picked from commit 37fc8e3171
)
This commit is contained in:
parent
8b6830f5bb
commit
78419bcb54
|
@ -31,7 +31,7 @@ workflows:
|
|||
type: 'tripleo.workflow.name', # Matches the workflow name
|
||||
payload: {
|
||||
status: 'STATUS', # One of RUNNING, SUCCESS, FAILED
|
||||
execution: {execution details}, # Deprecated and will be removed in the future.
|
||||
root_execution_id: 'UUID of the root execution',
|
||||
execution_id: 'UUID',
|
||||
message: "Human readable description",
|
||||
< Arbitrary data. This should match the workflow output data >
|
||||
|
@ -73,7 +73,7 @@ workflows:
|
|||
publish:
|
||||
branch:
|
||||
# The payload with arbitrary keys is merged with the status, message and execution.
|
||||
payload: <% {status => $.status, message => $.message, execution => $.execution, execution_id => $.execution.id, plan_name => $.plan_name, deployment_status => $.deployment_status} + $.payload %>
|
||||
payload: <% {status => $.status, message => $.message, root_execution_id => $.execution.root_execution_id, execution_id => $.execution.id, plan_name => $.plan_name, deployment_status => $.deployment_status} + $.payload %>
|
||||
next: prepare_messages
|
||||
|
||||
prepare_messages:
|
||||
|
|
Loading…
Reference in New Issue