In case of simplified parameter syntax expressions are not always evaluated properly
Bug #1396461 reported by
Renat Akhmerov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If we use something like
action: my_action param="
then the expression doesn't get evaluated properly.
If we use the same with "input" section then it works.
Changed in mistral: | |
milestone: | none → kilo-3 |
importance: | Undecided → Medium |
Changed in mistral: | |
status: | Fix Committed → Fix Released |
Changed in mistral: | |
milestone: | kilo-3 → 2015.1 |
To post a comment you must log in.
I can't reproduce this bug. "{$.farewell} , {$.name}"
Step to verify:
1. Write a simple workflow:
wf1:
type: reverse
input:
- farewell
tasks:
addressee:
action: std.echo output="John"
publish:
name: $
goodbye:
action: std.echo output=
requires: [addressee]
2. Create this wf using CLI and run execution with needed inputs and params.
3. Got "Task 'goodbye' [RUNNING -> SUCCESS, result = bye, John]"