openstack/deb-mistral
Code Issues Proposed changes

Fixing description of "mistral_http" action in DSL spec

Browse Source 
Change-Id: I53845f69427cc8e9cf9876b137a16144fac5de68
This commit is contained in:
Renat Akhmerov 2015-10-14 17:24:50 +06:00
parent ef2054b96b
commit b1ac75dddf
1 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/source/dsl/dsl_v2.rst
View File

@ -699,21 +699,26 @@ Example:
std.mistral_http
''''''''''''''''
This actions works just like 'std.http' with the only exception: when
This action works just like 'std.http' with the only exception: when
sending a request it inserts the following HTTP headers:
- **Mistral-Workflow-Name** - Name of the workflow that the current
action execution is associated with.
- **Mistral-Execution-Id** - Identifier of the workflow execution this
action is associated with.
- **Mistral-Task-Id** - Identifier of the task instance this action is
associated with.
- **Mistral-Task-Id** - Identifier of the task execution this action
execution is associated with.
- **Mistral-Action-Execution-Id** - Identifier of the current action
execution.
Using this action makes it possible to do any work in asynchronous
manner triggered via HTTP protocol. That means that Mistral can send a
request using 'std.mistral_http' and then any time later whatever
system that received this request can notify Mistral back (using its
public API) with the result of this action. Header **Mistral-Task-Id**
is required for this operation because it is used a key to find
corresponding task in Mistral to attach the result to.
public API) with the result of this action. Header
**Mistral-Action-Execution-Id** is required for this operation because
it is used a key to find corresponding action execution in Mistral
to attach the result to.
std.email
'''''''''