-
Allow user to pass
env
parameter topacks.setup_virtualenv
andpacks.install
action.This comes handy if user wants pip to use an HTTP(s) proxy (HTTP_PROXY and HTTPS_PROXY
environment variable) when installing pack dependencies. (new feature) -
Ability to view causation chains in Trace. This helps reduce the noise when using Trace to
identify specific issues. (new-feature) -
Filter Trace components by model types to only view ActionExecutions, Rules or TriggerInstances.
(new-feature) -
Include ref of the most meaningful object in each trace component. (new-feature)
-
Ability to hide trigger-instance that do not yield a rule enforcement. (new-feature)
-
Change the rule list columns in the CLI from ref, pack, description and enabled to ref,
trigger.ref, action.ref and enabled. This aligns closer the UI and also brings important
information front and center. (improvement) -
Action and Trigger filters for rule list (new-feature)
-
Add missing logrotate config entry for
st2auth
service. #2294 [Vignesh Terafast] -
Support for object already present in the DB for
st2-rule-tester
(improvement) -
Add
--register-fail-on-failure
flag tost2-register-content
script. If this flag is
provided, the script will fail and exit with non-zero status code if registering some resource
fails. (new feature) -
Add a missing
get_logger
method to the `MockSensorService. This method now returns an instance of
Mock`` class which allows user to assert that a particular message has been
logged. [Tim Ireland, Tomaz Muraus] -
Introduce a new
abandoned
state that is applied to executions that we cannot guarantee as
completed. Typically happen when an actionrunner currently running some executions quits or is
killed via TERM. -
Add new
st2garbagecollector
service which periodically deletes old data from the database
as configured in the config. By default, no old data is deleted unless explicitly configured in
the config. -
All published variables can be available in the result of ActionChain execution under the
published
property ifdisplay_published
property is specified. -
Allow user to specify TTL when creating datastore item using CLI with the
--ttl
option.
(improvement) -
Fix validation error when None is passed explicitly to an optional argument on action
execution. (bug fix) -
Deprecated
params
action attribute in the action chain definition in favor of the new
parameters
attribute. (improvement) -
Fix action parameters validation so that only a selected set of attributes can be overriden for
any runner parameters. (bug fix) -
Fix type in the headers parameter for the http-request runner. (bug fix)
-
Fix runaway action triggers caused by state miscalculation for mistral workflow. (bug fix)
-
Throw a more friendly error message if casting parameter value fails because the value contains
an invalid type or similar. (improvement) -
Use
--always-copy
option when creating virtualenv for packs from packs.setup_virtualenv
action. This is required when st2actionrunner is kicked off from python within a virtualenv. -
Fix a bug in the remote script runner which would throw an exception if a remote script action
caused a top level failure (e.g. copying artifacts to a remote host failed). (bug-fix) -
Display execution parameters when using
st2 execution get <execution id>
CLI command for
workflow executions. (improvement) -
Fix execution cancellation for task of mistral workflow. (bug fix)
-
Fix runaway action triggers caused by state miscalculation for mistral workflow. (bug fix)
-
The
--tasks
option in the CLI forst2 execution get
andst2 run
will be renamed to
--show-tasks
to avoid conflict with the tasks option in st2 execution re-run. -
Add option to rerun one or more tasks in mistral workflow that has errored. (new-feature)
-
Fix a bug when removing notify section from an action meta and registering it never removed
the notify section from the db. (bug fix) -
Make sure action specific short lived authentication token is deleted immediately when execution
is canceled. (improvement) -
Ignore lock release errors which could occur while reopening log files. This error could simply
indicate that the lock was never acquired. -
Replace
chatops.format_result
withchatops.format_execution_result
and remove dependency
on st2 pack from st2contrib. -
Trace also maintains causation chain through workflows.