StackStorm v3.2.0 released

May 1, 2020
By Eugen Cusmaunsa (@armab) and @punkrokk

It happened! 🎉 After a long wait, we’re more than excited to announce the StackStorm v3.2.0 release.

The StackStorm project has had some turbulent times since the previous release almost one year ago. The new v3.2.0 version is the first release since the project joined the Linux Foundation, formed new Governance, and gathered a new team of Maintainers. Considering the amount of changes happened, it looks like a big restart for the project.

It’s awesome for StackStorm to be under new governance. But that also means everything is on the Community’s shoulders now. And while it’s harder to rely only on the community’s efforts compared to the previously dedicated team of full-time employees, these days we’re observing increased number of contributors and interest from the larger organizations to adopt StackStorm Event Driven Automation and Automated Remediation. We hope this trend continues and we are striving for a better project future and further growth, together.

So what’s new in StackStorm 3.2.0?
This version aggregated almost one hundred changes including bugfixes, new Pack Dependencies, RHEL 8 / CentOS 8 Support, Orquesta retry and re-run features, ChatOps updates, Immutable parameters in Action Aliases, performance improvements, and more.


StackStorm Project Governance and Maintainers Update

Feb 20, 2020
By Eugen Cusmaunsa (@armab)

As you may heard before, StackStorm has joined the Linux Foundation.

Today we’re happy to update our Open Source Community with the news that first seeding StackStorm Technical Steering Committee (TSC) under the Linux Foundation was formed and ready to rock!

See and for more details, which you can find under the project Github repository stackstorm/st2. We’re back to git as a single source of truth. From now on adding new members or proposing a change to the project governance is a matter of opening a Pull Request, – check out #4856 PR.


StackStorm joins the Linux Foundation

StackStorm is headed for the Linux Foundation! This is a big move and we’re excited to share this news with our community. For several months now we’ve been working with the Linux Foundation, the StackStorm team, and many others inside Extreme to make this move possible. We want to thank everyone for their effort to make this move happen. 

StackStorm’s community continues to grow and the impact the project has had continues to show, and show, and show, and show (you get the point). We’re happy to continue this growth by joining the Linux Foundation, allowing us to include even more of our community in developing and governing StackStorm. 

You may be wondering what, if anything, will change with this move. The primarily change is how StackStorm is governed. Historically StackStorm’s development has been driven exclusively by Extreme Networks and the Extreme Workflow Composer team. Now, as a member of the Linux Foundation, we will be inviting others into this process by forming a Technical Steering Committee (TSC). The TSC will create and publish roadmaps, facilitate open standup meetings, and maintain StackStorm’s repositories. More in-depth details about how StackStorm will be governed can be found in our Technical Charter.

We’re excited about this move. It’s the next big step for StackStorm as a project and community. We look forward to working even closer with our community friends as we enhance and grow StackStorm. We’​re working on an FAQ to help answer any additional questions, and as always you can find us on the community Slack channel. 

StackStorm 3.1

StackStorm v3.1 is now available. This new release is focused on stability and bug fixes.

  • Update requests library to latest version (2.22.0) in requirements.
  • Disallow “decrypt_kv” filter to be specified in the config for values that are marked as “secret: True” in the schema.
  • Upgrade tooz library to latest stable version (1.65.0) so it uses latest version of grpcio library.
  • Fix timeout handling in the Python runner. In some scenarios where action would time out before producing any output (stdout, stder), timeout was not correctly propagated to the user.
  • Update st2common/ file so it correctly declares all the dependencies and script files it provides. This way st2-pack-* commands can be used in a standalone fashion just by installing st2common Python package and nothing else.
  • Fix st2-pack-download command so it works in the environments where sudo binary is not available (e.g. Docker).
  • Update st2-pack-install and st2-pack-download CLI command so it supports installing packs from local directories which are not git repositories.
  • Allow the orquesta st2kv function to return default for nonexistent key.
  • Fix orquesta st2kv to return empty string and null values.
  • Allow tasks defined in the same task transition with fail to run for orquesta.
  • Fix workflow service to handle unexpected coordinator and database errors.
  • Fix filter to_yaml_string to handle mongoengine base types for dict and list.
  • Microsoft Teams support in ChatOps is now considered generally available. This chat provider adapter does have some caveats and limitations however. Users are encouraged to read our documentation for Microsoft Teams before switching to it.


As always, make sure you have backups first. Then follow the standard Upgrade Instructions.

ST2 Exchange – A BeerTab Pack??

June 20, 2019
by Lindsay Hill

StackStorm can’t pour you a beer. But now it can keep track of who owes you a beer! Read on for more info about the new beertab pack, and other new packs & interesting StackStorm Exchange updates.


Running Orquesta Serverless

6/18/2019 by m4dcoder

Orquesta is the new workflow engine in StackStorm. If you are on the fence choosing which workflow services to use from AWS, Azure, or GCP and you are thinking that this post is too long to read, then just skip ahead and run StackStorm.


Machine Learning driven Closed Loop Automation

June 12, 2019
By Benoit Lourdelet

The agility at which the business can respond to real-life situations is proportional to the level of digitization that has been implemented in the business. For a business to nimble and agile, it is imperative that all the processes be delivered as a digital service that can be provisioned, monitored and remediated by an automation logic at the core of the business. The automation logic should follow the Monitor, Assess, Plan and Execute (MAPE) loop methodology to provide a complete closed-loop automation system for the digital business. Click below to see a video demonstrating using StackStorm with Machine Learning to do this.


Dmitri says “good bye”

by Dmitri Zimine

Dear StackStorm. You have grown up. The time has come for us to part ways. You will continue the life of mature, established open-source project, with growing community. I will step aside, watch with pride your successes, and be always here to help when you need me. READ MORE…

StackStorm v3.0.1

May 30, 2019
By Tomaz Muraus

Today we are happy to announce StackStorm v3.0.1.

This is a first bug fix patch / patch release in the v3.0.x release series. It includes the following bug fixes and improvements:

  • Fix a bug in the remote command and script runner so it correctly uses SSH port from a SSH config
    file if ssh_runner.use_ssh_config parameter is set to True and if a custom (non-default)
    value for SSH port is specified in the configured SSH config file
  • Update pack install action so it works correctly when python_versions pack.yaml metadata attribute is used in combination with --python3 ” st2 pack install” flag.
  • Add source_channel back to the context used by Mistral workflows for executions which are triggered via ChatOps (using action alias). In StackStorm v3.0.0, this variable was inadvertently removed from the context used by Mistral workflows.
  • Fix a bug with timestamp attribute in the execution.log attribute being incorrect when server time where st2api is running was not set to UTC.
  • Fix a bug with some packs which use --python3 flag (running Python 3 actions on installation where StackStorm components run under Python 2) which rely on modules from Python 3 standard library which are also available in Python 2 site-packages (e.g. concurrent) not working correctly. In such scenario, package / module was incorrectly loaded from Python 2 site-packages instead of Python 3 standard library which broke such packs.
  • Remove policy-delayed status to avoid bouncing between delayed statuses in st2scheduler service.
  • Truncate some database index names so they are less than 65 characters long in total. This way it also works with AWS DocumentDB which doesn’t support longer index name at the moment.

    NOTE: AWS DocumentDB is not officially supported. Use at your own risk.
  • Fix a possible shell injection in the linux.service action. User who had access to run this action could cause a shell command injection by passing a compromised value for either the service or action parameter.


Thanks to everyone who has contributed to this release.

Special thanks to James Robinson (Netskope and Veracode) for reporting the security issue in linux.service action.


As always, make sure you have backups first. Then follow the standard Upgrade Instructions.

It’s Here: StackStorm 3.0

April 29, 2019

By Lindsay Hill

It’s here at last: StackStorm 3.0. This is a big release for us: Orquesta is GA, and Workflow Designer has a great new look & feel, massively improving usability. We’ve added Microsoft Teams support, Inquiries also goes GA, and more. Here’s all the details: READ MORE…