On 26 Feb 2014, at 16:30, Dmitri Zimine wrote:
> My understanding, correct me if I'm missing the intention:
>
> Action are defined as code, aka REST_API or SEND_EMAIL.
> These are base actions, they are analogous to function definitions.
>
> Tasks is a set of parameters for the action.
>
>
On 26 Feb 2014, at 15:18, Timur Nurlygayanov wrote:
> for me just unclear the following syntacsis:
> $.image_id
> what is $ in this case? It will be more clear if we can replace $ to
> something - any instance with readable name, like global.image_id or
> context.image_id.
> looks like $ can b
My understanding, correct me if I'm missing the intention:
Action are defined as code, aka REST_API or SEND_EMAIL.
These are base actions, they are analogous to function definitions.
Tasks is a set of parameters for the action.
Actions can be also defined declaratively, under Services, based
Timur, '$' here is mean referrence to context at stage which it has been
given to.
'$.image_id' takes 'image_id' from current workflow execution context
variable
On Wed, Feb 26, 2014 at 12:30 PM, Nikolay Makhotkin wrote:
> Hi, Renat!
>
>
>
> *Suggestions*
>> *1*. Define "input" and "output" at
Hi, Renat!
*Suggestions*
> *1*. Define "input" and "output" at task level like this:
> createVM:
>input:
> image_id: $.image_id
>output: vm_id
> Where "output: vm_id" is basically a replacement for "store-as: vm_id" at
> action level, i.e. it's a hint to Mistral to
Hi Renat,
for me just unclear the following syntacsis:
$.image_id
what is $ in this case? It will be more clear if we can replace $ to
something - any instance with readable name, like global.image_id or
context.image_id.
looks like $ can be the different in different name spaces.
it will be uncl
Hi team,
I’m currently working on the first version of Data Flow and I would like to
make sure we all clearly understand how to interpret “parameters" for tasks and
actions when we declare them in Mistral DSL. I feel like I’m getting lost here
a little bit. The problem is that we still don’t ha
