preserve key order in workflow definition
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Oleg Ovcharuk |
Bug Description
It is very important to save workflow definitions "as is", without any changes.
If user creates one workflow by request, Mistral saves it correctly, but if there are multiple workflows in one request, Mistral perform double conversion to separate workflow definitions from one yaml. In this case keys of incoming yaml could be sorted, which could broke user's business.
Test case:
wfs.yaml
version: "2.0"
wf1:
tasks:
task1:
action: std.noop
publish:
we: 1
dont_want: 2
wf2:
tasks:
task1:
action: std.noop
1) Create these workflows by one request.
2) Get workflow definition of wf1
Expected:
version: "2.0"
wf1:
tasks:
task1:
action: std.noop
publish: {we: 1, dont_want: 2, to_be_sorted: 3}
Actual:
version: "2.0"
wf1:
tasks:
task1:
action: std.noop
publish: {dont_want: 2, to_be_sorted: 3, we: 1}
Changed in mistral: | |
assignee: | nobody → Oleg Ovcharuk (vgvoleg) |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → stein-3 |
Changed in mistral: | |
milestone: | stein-3 → train-1 |
Changed in mistral: | |
milestone: | train-1 → ussuri-1 |
Changed in mistral: | |
milestone: | ussuri-1 → ussuri-2 |
Fix proposed to branch: master /review. openstack. org/636583
Review: https:/