Go to file
ali 20c3408692 Add namespaces to Ad-Hoc actions
added namespace for the actions, actions can have the same name if they
 are not in the same namespace, when executing an action, if an action
 with that name is not found in the workflow namespace or given
 namespace mistral will look for that action in the default namespace.

  * action base can only be in the same namespace,or in the
    default namespace.
  * Namespaces are not part of the mistral DSL.
  * The default namespace is an empty string ''.
  * all actions will be in a namespace, if not specified, they will be
    under default namespace

Depends-On: I61acaed1658d291798e10229e81136259fcdb627
Change-Id: I07862e30adf28404ec70a473571a9213e53d8a08
Partially-Implements: blueprint create-and-run-workflows-within-a-namespace
Signed-off-by: ali <ali.abdelal@nokia.com>
2020-01-07 08:10:53 +00:00
2018-01-31 04:16:42 +00:00
2019-11-14 13:42:56 +00:00
2020-01-07 08:10:53 +00:00
2019-04-19 19:37:05 +00:00
2018-05-30 14:46:25 -04:00
2017-07-27 22:15:12 +08:00
2013-12-30 13:11:49 +07:00
2019-10-18 12:42:12 +08:00
2019-10-23 09:26:22 +00:00
2017-03-03 10:17:44 +00:00

Team and repository tags

image

Mistral

Workflow Service for OpenStack cloud. This project aims to provide a mechanism to define tasks and workflows without writing code, manage and execute them in the cloud environment.

Project Resources

Description
Workflow Service for OpenStack.
Readme 52 MiB
Languages
Python 99%
Shell 0.9%