Remove all internal WF context data from final WF output
Bug #1648425 reported by
Renat Akhmerov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Renat Akhmerov |
Bug Description
If we have a WF where 'output' field is not defined explicitly then all WF context is treated as its output. But some of the data we put into the context is for internal purposes only.
Example:
For the worklflow:
my_wf:
tasks:
task1:
action: std.echo output="Hi Mistral!"
on-success: task2
task2:
action: std.noop
we will have output:
{
"__
"id": "ee3f896b-
"name": "task2"
}
}
The key "__task_execution" should not be in it because it's a internal temporary data.
Changed in mistral: | |
importance: | Undecided → Medium |
milestone: | none → ocata-2 |
status: | New → Confirmed |
Changed in mistral: | |
milestone: | ocata-2 → ocata-3 |
Changed in mistral: | |
assignee: | nobody → Renat Akhmerov (rakhmerov) |
Changed in mistral: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in mistral: | |
milestone: | ocata-rc1 → ocata-rc2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/432215
Review: https:/