Releases: StackStorm/st2
Releases · StackStorm/st2
0.11.2 - June 12, 2015
- Fix a bug with start_timestamp and end_timestamp sometimes returning an invalid value in a local instead of UTC timezone. (bug-fix)
- Fix to get PollingSensor working again. Sensors of type PollingSensor were not being treated as such and as a result would fail after the 1st poll. (bug-fix)
v0.11.1 June 8, 2015
- Allow user to filter executions on trigger instance id. [Sayli Karmarkar]
- Action aliases are registered by default. (improvement)
- Repair failing pack installation. (bug-fix)
v0.11 June 5, 2015
- Allow user to configure the CLI using an ini style config file located at
~/.st2rc
.
(new-feature) - Add support for caching of the retrieved auth tokens to the CLI. (new-feature)
- Throw a more-user friendly exception when enforcing a rule if an action referenced inside
the rule definition doesn't exist. (improvement) - Fix a bug with the rule evaluation failing if the trigger payload contained a key with a
dot in the name. (bug-fix) - Fix a bug with publishing array (list) values as strings inside the action chain workflows.
(bug-fix) - Update CLI so it displays the error at the top level when using
run
,execution run
or
execution get
when executed workflow fails. (improvement) - Action trigger now contains execution id as opposed to liveaction id. (bug-fix)
- Add new API endpoint for re-running an execution (
POST /executions/<id>/re_run/
).
(new-feature) - Rules should be part of a pack. (improvement)
- Update Windows runner code so it also works with a newer versions of winexe (> 1.0).
(improvement)
[James Sigurðarson] - CLI now has
get
andlist
commands for triggerinstance. (new-feature) - Validate parameters during rule creation for system triggers. (improvement)
- CLI now has
re-emit
command for triggerinstance. (new-feature)
v0.9.2 - May 26, 2015
- Fix broken packs.download action. (bug-fix)
v0.9.1
v0.9.0
- Report a more user-friendly error if an action-chain task references an invalid or inexistent
action. Also treat invalid / inexistent action as a top-level action-chain error. (improvement) - Report a more user-friendly error if an action-chain definition contains an invalid type.
(improvement) - Enable authentication by default for package based installations.
- Rename all st2 processes to be prefixed by st2. (sensor_container is now st2sensorcontainer,
rules_engine is now st2rulesengine, actionrunner is now st2actionrunner) (improvement) - Return a user friendly error on no sensors found or typo in sensor class name in single
sensor mode. (improvement) - Sensor container now returns non-zero exit codes for errors. (bug-fix)
- Check if internal trigger types are already registered before registering
them again. (improvement) - Sensor container now can dynamically load/reload/unload sensors on data model changes.
(new-feature) - Fix a bug in datastore operations exposed in st2client. (bug-fix)
- Catch exception if rule operator functions throw excepton and ignore the rule. (bug-fix)
- Remove expected "runnertype not found" error logs on action registration
in clean db. (improvement) - Clean up rule registrar logging. (improvement)
- Add
-t
/--only-token
flag to thest2 auth
command. (new-feature) register
param in packs.install should be passed to packs.load. (bug-fix)- Fix validation code to validate value types correctly. (bug-fix)
- Add ability to best-effort cancel actions and actionchain via API. (new-feature)
- Add new
windows-cmd
andwindows-script
runners for executing commands
and PowerShell scripts on Windows hosts. (new-feature) - Update runner names so they follow a consistent naming pattern. For backward
compatibility reasons, runners can still be referenced using their old names.
(improvement) - Update all the Python services to re-open log files on the
SIGUSR1
signal. (new-feature) - Internal trigger types registered using APIs should use auth token. (bug-fix)
v0.8.3
v0.8.2
- Fix a bug with python-runner actions sometimes not correctly reporting the action's
stdout
.
(bug-fix) - Fix a bug in the
run-remote-script
runner - the runner ignored environment variables and
authentication settings which were supplied to the action as parameters. (bug-fix)
v0.8.1
- Allow user to exclude particular attributes from a response by passing
?exclude_attributes=result,trigger_instance
query parameter to the/actionexecutions/
and/actionexecutions/<execution id>/
endpoint (new-feature) - Add new
/actionexecutions/<id>/attribute/<attribute name>
endpoint which allows user to
retrieve a value of a particular action execution attribute. (new-feature) - Update
execution get
CLI command so it automatically detects workflows and returns more
user-friendly output by default. (improvement) - Update
run
,action execute
,execution get
andexecution re-run
CLI commands to
take the same options and return output in the same consistent format. - Fix a bug with http runner not parsing JSON HTTP response body if the content-type header also
contained a charset. (bug-fix) - Indent workflow children properly in CLI (bug-fix)
- Make sure that wait indicator is visible in CLI on some systems where stdout is buffered. (bug-fix)
- Fix a bug with
end_timestamp
attribute on theLiveAction
andActionExecution
model
containing an invalid value if the action hasn't finished yet. (bug-fix) - Correctly report an invalid authentication information error in the remote runner. (bug-fix)
- Throw a more friendly error in the action chain runner if it fails to parse the action chain
definition file. (improvement) - Fix a bug in the action chain runner and make sure action parameters are also available for
substitution in thepublish
scope. (bug-fix)
v0.8.0
- Allow user to specify current working directory (
cwd
parameter) when running actions using the
local or the remote runner (run-local
,run-local-script
,run-remote
,
run-remote-script
). (new-feature) - Default values of the parameter of an Action can be system values stored in kv-store. (new-feature)
- Allow users to specify additional paths where StackStorm looks for integration packs using
packs_base_paths
setting. (new-feature) - Allow user to specify which Python binary to use for the Python runner actions using
actionrunner.python_binary
setting (new-feature) - Default Python binary which is used by Python runner actions to be the Python binary which is
used by the action runner service. Previous, system's default Python binary was used. - Fix a race-condition / bug which would occur when multiple packs are installed at the same time.
(bug-fix) - Vars can be defined in the ActionChain. (new-feature)
- Node in an ActionChain can publish global variables. (new-feature)
- Allow user to provide authentication token either inside headers (
X-Auth-Token
) or via
x-auth-token
query string parameter. (new-feature) - Allow actions without parameters. (bug-fix)
- Fix a bug with rule matching not working for any triggers with parameters. (bug-fix)
- Require
cmd
parameter for the following actions:core.remote
,core.remote_sudo
,
core.local
,core.local_sudo
(bug-fix) - Allow user to override authentication information (username, password, private key) on per
action basis for all the remote runner actions. (new-feature) - Allow user to pass
--inherit-env
flag to thest2 action run
command which causes all
the environment variables accessible to the CLI to be sent asenv
parameter to the action
being executed. (new-feature) - Cast params of an execution before scheduling in the RulesEngine. This allows non-string
parameters in an action. (new-feature) - Use QuerySet.count() instead of len(QuerySet) to avoid the caching of the entire result which
improve running time of API request. (bug-fix) - CLI commands to return non-zero exit codes for failed operations (new-feature)
- Fix a bug with template rendering, under some conditions, ending in an infinite loop. (bug-fix)
- Rename ActionExecution to LiveAction. (refactor)
- Rename ActionExecutionHistory to ActionExecution. (refactor)
- A separate history process is no longer required. ActionExecution updates are carried at time of
update to LiveAction. (refactor) - Add new
nequals
(neq
) rule criteria operator. This criteria operator
performs not equals check on values of an arbitrary type. (new-feature) - Mistral subworkflows kicked off in st2 should include task name. (bug-fix)
- Add new
execution re-run <execution id>
CLI command for re-running an
existing action. (new-feature) - Dispatch an internal trigger when a sensor process is spawned / started
(st2.sensor.process_spawn
) and when a process exits / is stopped
(st2.sensor.process_exit
). (new-feature) - Update HTTP runner to automatically parse JSON response body if Content-Type is
application/json
(new-feature) - API url /v1/actionexecutions/ is now deprecated in favor of /v1/executions/ (refactor)
- API url change /v1/history/execution to /v1/executions (refactor)
- API url change /v1/history/execution/views/filters to /v1/executions/views/filters (refactor)
- POST to /v1/executions take LiveActionAPI but returns ActionExecutionAPI (refactor)
- Support for filtering by timestamp and status in executions list. (new-feature)
- Execution list shows only top level executions by default to see full list use --showall. (refactor)
- Ability to see child tasks of any execution. (new-feature)
- Allow sensors to manage global datastore items via sensor_service by passing
local=False
argument to theget_value
,set_value
anddelete_value
methods. (new-feature) - Allow sensors to list datastore items using
list_values
sensor_service method. (new-feature) - Allow users to filter datastore items by name prefix by passing
?prefix=<value>
query
parameter to the /keys endpoint. (new-feature) - Fix non-string types to be rendered correctly in action parameters when used in rule. (bug-fix)
- Allow user to specify default value for required attributes in the definition of action
parameters. (bug-fix) - When running with auth enabled, correctly preserve the username of the authenticated user who
has triggered the action execution. (bug-fix)
Read more on our blog, w/ simple GIF demos of the highlight of 0.8 - our first release of the StackStorm GUI here: http://stackstorm.com/2015/03/03/stackstorm-0-8-introducing-new-web-ui/