Mistral saves whole yaml for every wf definition in case of creating multiple wf.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Oleg Ovcharuk |
Bug Description
Whenever we want to save multiple wf from one yaml, every saved wf will have all this input in their definitions. This behavior doesn't match with saving one wf. This could be bad for users, who want to parse definition.
For example:
I want to create two workflows from file wfs.yaml
"""
version: '2.0'
wf1:
type: direct
tasks:
task1:
action: std.noop
wf2:
type: direct
tasks:
task1:
action: std.noop
"""
mistral workflow-
Expected output:
"""
version: '2.0'
wf1:
type: direct
tasks:
task1:
action: std.noop
"""
Actual output:
"""
version: '2.0'
wf1:
type: direct
tasks:
task1:
action: std.noop
wf2:
type: direct
tasks:
task1:
action: std.noop
"""
The same behavior appears when I want to update wfs.
summary: |
- Mistral saves wrong wf definition in case of creating multiple wf + Mistral saves whole yaml for every wf definition in case of creating + multiple wf. |
description: | updated |
Changed in mistral: | |
milestone: | none → stein-1 |
importance: | Undecided → Medium |
assignee: | nobody → Oleg Ovcharuk (vgvoleg) |
status: | New → Confirmed |
Fix proposed to branch: master /review. openstack. org/603208
Review: https:/