Zed Series Release Notes¶
4.4.0¶
New Features¶
The new
enforce_raw_definitionsvariable has been added to theClientclass and eachResourceManagerclass. This variable is set to False by default. Setting this parameter to True enforces the client to usedefinitionpassed in as raw content.
4.0.0¶
New Features¶
Add namespace parameter to action commands. Namespace parameter allows to create multiple actions with same name under different namespaces.
Added 2 new CLI commands, “execution-get-sub-executions” returns sub-executions of a given execution id and “task-get-sub-executions” returns the sub-executions of a given task execution id. Both commands have the options “–max-depth” which is the max depth of a sub-execution, and “–errors-only” that allows to find only ERROR paths of the execution tree.
Upgrade Notes¶
Python 2.7 support has been dropped. Last release of python-mistralclient to support python 2.7 is OpenStack Train. The minimum version of Python now supported is Python 3.6.
3.8.0¶
New Features¶
Added the new CLI command “execution-get-report” that prints information about the entire workflow execution tree, including its task executions, action executions and nested workflow executions. The command currently has filters “–errors-only” that allows to find only ERROR paths of the execution tree (enabled by default), “–no-errors-only” that allows to print all tree regardless of the elements’ state, “–max-depth” that allows to limit the depth of the tree that needs to be printed. This command should be especially useful for debugging failure situations when it’s not easy to manually track down to the root cause.
Add namespace parameter to workbook commands. Namespace parameter allows to create multiple workbooks with same name under different namespaces.
Critical Issues¶
The default behavior of the action-execution-list, execution-list and task-list commands has been changed. Instead of returning the oldest N records (default 100 or –limit specified value) by default, they now return the most recent N records, when no other sort_dir, sort_key or marker values are provided. If the user specifies –oldest or any of the –marker, –sort_key or –sort_dir options, the new behavior is disabled and the commands will work according to the user-supplied options.
3.6.0¶
Bug Fixes¶
mistralclient 3.5.0 introduced a new –force option to delete executions that are still running. However, this had the unintended impact of passing force=false when it wasn’t provided. This is incompatible with previous releases of the Mistral API which reject requests as they don’t recognise “force”.
3.5.0¶
New Features¶
Adding a –force optional parameter to delete excetutions. Without it only finished executions can be deleted. If –force is passed the execution will be deleted but mistral will generate some errors as expected objects in memory no longer exist
3.2.0¶
New Features¶
Using namespaces is now supported from the client. It is possible to use the namespace flag with all workflows commands and when creating a workflow execution. Namespace feature allows a user to add two workflows with the same name to Mistral as long as they are within two different namespaces. Namespace will also be visible in the table printed when using the CLI to get info about workflows. Plus, the CLI will print the workflow namespace along with the workflow name where needed.
Other Notes¶
The dependency to python-keystoneclient was removed. Relying solely on keystoneauth1.
The user has to set the “OS_USER_DOMAIN_NAME” and “OS_PROJECT_DOMAIN_NAME” explicitly if keystone v3 version is being used.
3.1.1¶
Critical Issues¶
The “–limit” parameter of heavy CLI commands like “task-list” and “execution-list” and “action-execution-list” is set to “100” by default to avoid the huge load on server. To fetch the full result set, user may use “–limit -1”.
3.1.0¶
Bug Fixes¶
--os-region-nameorOS_REGION_NAMEis fully supported now and will be passed to Mistral service in order to get OpenStack service client for the specific region.
