The 'join' example for using a number did not have a proper workflow.
It looks like it was copied from the 'all' example and not completely
changed. Also, disambiguate the wording of the description for that
example. It used the word 'once' in a place where it looked as though
it meant 'one time' instead of 'as soon as'.
Change-Id: I9b89768c0f0b7d325db08ea9345965a9263a64c8
Closes-Bug: #1761827
Fixes the bug where calling std.ssh action without "password" input was resulting in error.
Closes-bug: #1756272
Change-Id: I5f7af13326933658014a9c42c495d779bec7f14f
Usage of break-on and continue-on are not very clear. This hopefully
gives some pointers on their usage.
Change-Id: Ide237a23ab85fac7342a8fc9bf748fd0b78bf41d
* verified the length of task name while creating a workflow
* fixed bug when join task has a long name
* added the length limitation to the spec docs
Change-Id: I233e6b0f30d42b939757e9c1caf4965ecc375aee
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
This may be useful for a testing purpose if you want to emulate a
action error with data for timeout, retry and the rest of task policies
Change-Id: I679b8338dade284817000670e96ab108481372ae
Signed-off-by: Vitalii Solodilov <mcdkr@yandex.ru>
This allows for filtering or executions
Implements: blueprint mistral-workflow-executions-yaql-function
Change-Id: I8d41c662d8659375750b52f7510e9a35f8b42f93
Evaluate action names dynamically, so yaql or jinja expression can be
used
Change-Id: I48761c215f0255976c330ffa34f27bb695c944a9
Implements: blueprint mistral-dynamic-actions
In the file doc/source/user/dsl_v2.rst, the json format of
task publish result is not well formated, this change is to
pretty format the json code block
Change-Id: I783472c1d7c13cd7b6a464325cf7213abf3ac359
Evaluate workflow names dynamically, so yaql or jinja expression
is allowed as sub-workflow name. Tasks names are not yet
dynamically evaluated.
Partially implements: blueprint mistral-dynamic-actions
Change-Id: Icfe591e27a4f45c2e3dcfa83512217f3b2122189