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>
15 lines
544 B
YAML
15 lines
544 B
YAML
---
|
|
features:
|
|
- |
|
|
Add support for creating ad-hoc actions in a namespace. Creating actions
|
|
with same name is now possible inside the same project now. This feature
|
|
is backward compatible.
|
|
|
|
All existing actions are assumed to be in the default namespace,
|
|
represented by an empty string. Also, if an action is created without a
|
|
namespace specified, it is assumed to be in the default namespace.
|
|
|
|
If an ad-hoc action is created inside a workbook, then the namespace of the workbook
|
|
would be also it's namespace.
|
|
|