StackStorm v3.3.0 Released

Oct 22, 2020

by Nick Maludy (@nmaludy) and @blag

The StackStorm project is pleased to announce that the latest version of StackStorm, v3.3.0, is now publicly available! It has been approximately 5 months since our v3.2.0 release and we are releasing a new version containing important features and bug fixes that move the project forward.


With this release we’re driving toward several project goals on the StackStorm roadmap. Each of the goals in this release is focused on providing better maintainability and ease of long-term support for the project. Reducing maintenance burden on the development team allows us to put more effort into features.

So, what changed?

Dropped Support for RHEL6

Red Hat Enterprise Linux/CentOS 6 is reaching the end of its maintenance lifecycle on November 20, 2020. This OS also has some oddities and legacy baggage that makes it a drag on the team with lots of weird conditionals and edge cases. Back in the StackStorm v3.2.0 release announcement we warned users of our plans to deprecate RHEL/CentOS 6 and today we’re happy to announce that we’ve dropped support for RHEL/CentOS 6! Good news is, we support both RHEL/CentOS 7 and 8.

Dropped Support for HipChat in ChatOps

Atlassian discontinued HipChat Cloud back in Febuary 2019, and now HipChat Server has gone end-of-life as of June 2020. It is recommended by Atlassian to migrate over to Slack as the chat platform of the future, we couldn’t agree more! Since it’s time to move on, we’ve dropped support for HipChat from st2chatops. Thanks for the good memories HipChat!

Deprecation Notice for Python 2

Oh Python 2, you’ve been a long standing friend but your time has also come. Python 2 was end-of-life on January 1, 2020. As of StackStorm v3.3.0 we are beginning the process of deprecating Python 2 and migrating to Python 3. StackStorm already supports Python 3 for its own code base on RHEL/CentOS 8 and Ubuntu 18.04, and it also supports executing Python actions using Python 3. We will begin the work to migrate existing platforms to using Python 3 exclusively and be dropping support for Python 2. Sorry this has taken so long, but both Operating Systems and 3rd party packages that StackStorm depends on have taken a long time to add Python 3 support, we’ve mostly been blocked by them.

Starting with StackStorm v3.3.0 users will now see warnings on the st2ctl CLI if it is being executed from a Python 2 runtime.

$ st2ctl status

Deprecation warning: Support for python 2 will be removed in future StackStorm releases. Please ensure that all packs used are python 3 compatible. Your StackStorm installation may be upgraded from python 2 to python 3 in future platform releases. It is recommended to plan the manual migration to a python 3 native platform, e.g. Ubuntu 18.04 LTS or CentOS/RHEL 8.

There will also be a warning printed in the StackStorm system service logs (st2api, st2actionrunner, etc):

Sep 17 14:14:13 testsyslog st2workflowengine[14015]: 2020-09-17 14:14:13,852 WARNING [-] DEPRECATION WARNING. Support for python 2 will be removed in future StackStorm release(s). Please ensure that all packs used are python 3 compatible. Python 3 will already be used if you upgrade to a newer OS release

On the pack side of the house, a warning will be printed when installing a pack that only supports Python 2:

$ st2 pack install python2only
    [ succeeded ] init_task
    [ succeeded ] download_pack
    [ succeeded ] make_a_prerun
    [ succeeded ] get_pack_dependencies
    [ succeeded ] check_dependency_and_conflict_list
    [ succeeded ] download_pack
    [ succeeded ] make_a_prerun
    [ succeeded ] get_pack_dependencies
    [ succeeded ] check_dependency_and_conflict_list
    [ succeeded ] install_pack_requirements
    [ succeeded ] get_pack_warnings
    [ succeeded ] register_pack

| ref         | name        | description      | version | author           |
| python2only | python2only | Pack for python2 | 0.0.1   | StackStorm       |

DEPRECATION WARNING: Pack Test2 only supports Python 2.x. ST2 will remove support for Python 2.x in a future release.

Stay tuned to our blog for an upcoming post detailing our plans for Python 2 deprecation and transition to Python 3!

Deprecation of Chef Deployment

Our Chef installation method chef-stackstorm hasn’t received an update in some time and currently has no maintainer. As of right now, this installation method is deprecated and is no longer supported. If you are a Chef developer and want to pick up support for this installation method, please get in touch by joining the #chef channel in our Slack community .

Overhaul of st2-docker

The Docker installation method st2-docker received an update recently. Its docker-compose file now pulls containers from the st2-dockerfiles repository. This is a positive step forward because now st2-docker now uses the same containers as our Kubernetes helm chart installation method stackstorm-ha.

MongoDB 4.0

MongoDB 4.0 is currently the default database on both RHEL/CentOS 8 and Ubuntu 18.04. In an effort to standardize our support matrix across the various operating systems, we’re now updating MongoDB to 4.0 on all OSes. This means that if you’re running RHEL/CentOS 7 or Ubuntu 16.04, you’ll need to upgrade from MongoDB 3.4 to MongoDB 4.0. However, there is a catch!

When upgrading your RHEL/CentOS 7 or Ubuntu 16.04 system from MongoDB 3.4 to MongoDB 4.0 it is not a direct path. In order to perform this upgrade successfully one will need to first upgrade MongoDB 3.4 to MongoDB 3.6 and then to MongoDB 4.0. These special instructions, including actual commands to run, can be found in our Version Specific Upgrade Scripts section of the StackStorm documentation. If you’re a Puppet Bolt user, we have a st2::upgrade_mongodb Plan available to perform these steps in an automated way:

mkdir modules
git clone modules/st2
bolt plan run st2::upgrade_mongodb --targets stackstormhost.domain.tld

Mistral Removal

OpenStack Mistral was previously used as StackStorm’s primary workflow engine. Almost two years ago, back in StackStorm v2.10 Mistral deprecation was announced and now in v3.3.0 Mistral has been fully removed from StackStorm. Where do we go from here?

In case you haven’t heard, StackStorm has developed its own workflow engine called Orquesta. If you’re currently still using Mistral for your workflows, we’ve developed a tool to help ease the transition from Mistral to Orquesta called orquestaconvert. It is super easy to get started:

$ git clone
$ cd orquestaconvert

You can convert a single workflow:

$ ./bin/ ../stackstorm-mypack/actions/workflows/nasa_apod_twitter_post.yaml

Or, even better, convert all of the workflows in a pack:

$ ./bin/ --action-dir ../stackstorm-mypack/actions


  • Stripping of authentication headers in webhooks
  • ssh timeouts
  • st2 bug fixes
  • orquesta bug fixes
  • st2web dependencies and security updates

There are so many more bug fixes and small changes that including them in this list would make the blog post huge. If you’re interested in learning more, see a complete list of all changes across our various repositories in our discussion post for the v3.3.0 release.

Future Plans

With all of these house-cleaning items off our plate, the StackStorm team is excited about our future plans, below is a list of items that may be coming in a future versions:

  • Add support for Ubuntu 20.04
  • Migration from Python 2 to Python 3
  • RBAC functionality (previously enterprise-only)
  • Integrate st2flow workflow composer into the Web UI  (previously enterprise-only)
  • Converting ChatOps from Javascript to Python
  • and more!

If you’re interested in learning about the other ideas we have for the future and would like to help, please checkout our roadmap documentation.

Calling All JavaScript Developers!

StackStorm’s front end web UI, st2web, could really use some help and maintenance. If you are a JavaScript developer or know someone who is looking to help out on an Open Source project, we would love to have you! Please come join our Slack community and we can help you get started.

Get Involved!

The StackStorm project is actively seeking more community contributions. There are so many ways to get started:

Thank you so much and happy automating!

Ansible StackStorm role v2.0.0 released

By Amanda McGuinness of Ammeon Solutions

Ansible-st2 v2.0.0We’re very excited to announce that Ansible roles to deploy StackStorm have been promoted to new major version 2.0.0! 

There has been a lot of activity recently on the ansible-st2 repository, with 4 releases in the last couple of months. Ansible can now be used to deploy StackStorm on more modern operating systems and with newer third-party applications.


2020 ChatOps User Survey

August 3rd, 2020
by @blag

The 2020 ChatOps User Survey is here! This is your chance to submit your feedback on using ChatOps with StackStorm – what we get right, what we get wrong, and what we need to focus on.

We will use this feedback to chart the development roadmap for ChatOps, whether that means leaving st2chatops as-is, or focusing on supporting more chat providers, deeper feature support for specific providers, improving ChatOps integration with the rest of StackStorm (RBAC for ChatOps!), or even rewriting the entire thing on top of Errbot or OpsDroid.

Your feedback is valuable to us, especially now that all of StackStorm is open source, since it will allow us to cater our efforts towards what matters the most to you. Are you running ChatOps as a hubot plugin to your own hubot instance? Have you extended ChatOps to use your own chat provider? Are you running a different ChatOps service? Do you want to use machine learning driven artificial intelligence to securely empower natural language understanding and disrupt established technology while creating a digital transformation and revolutionizing paradigms in the cloud on the blockchain? We want to hear from you!

Please take a few minutes out of your day to fill out 2020 ChatOps User Survey and/or leave us a kind note or some words of encouragement. The survey will close at noon (PDT) on August 31st, so leave your feedback soon!

The survey is here:

Once you’re finished, you can also help us out by sponsoring the StackStorm project and contributing code.

Sponsoring StackStorm

Jun 12, 2020
by StackStorm Team

Sponsoring StackStorm at Community Brdige

In recent news Extreme Networks open-sourced EWC and contributed all previously “enterprise only” features to the StackStorm project operating under the Linux Foundation.

This is very exciting news for the project’s future and its users. It also means that StackStorm’s destiny now rides on the shoulders of the community along with organizations that rely on it in their production infrastructure and benefit from the project’s unique event-driven-automation and automated remediation capabilities.READ MORE…

Extreme Networks Donates EWC To Linux Foundation

May 27, 2020
By @blag

After acquiring the StackStorm product and the amazing StackStorm team in 2017 from Brocade, Extreme Networks has been a large contributor (if not the largest contributor) to the StackStorm project, even donating the code and transferring the StackStorm trademarks to the Linux Foundation last year. Continuing that tradition, Extreme Networks announced today that they were donated their enterprise extensions of StackStorm (previously StackStorm Enterprise) to the Linux Foundation! The contribution includes the Extreme Workflow Composer (EWC), the graphical workflow editor, as well as their LDAP, RBAC, and SSO plugins. With these contributions, adopting StackStorm in your organization has never been easier!

Now that all parts of StackStorm are open source, you can expect a better installation and configuration experience in future releases, and a lower barrier to entry for users who are just getting started with automating tasks. The authentication and authorization plugins will enable better security and integration with your existing mechanisms, and now that the workflow composer is open source, StackStorm’s user interface will be more integrated and streamlined. It will soon be possible for anybody to create and modify Orquesta workflows entirely with their web browser!

And if you know any frontend developers who would enjoy working on a React app with an existing and excited userbase, please have them stop by and say hi! We need support from the StackStorm community now more than ever, to help integrate and improve the product, but also to help package all of the new code up for end users, to provide migrations paths for users to the new open source releases, and to integrate the EWC documentation into the StackStorm documentation. There’s plenty of work to go around, so please pitch in and help out!

We’re very excited about this big update. It’s a huge change for the project and our community. We hope it’ll help even more organizations to improve their automation with no more barriers to contribute back to StackStorm Open Source under the Linux Foundation neutral home!

In the meantime, please tweet your gratitude to Extreme Networks for their contribution!

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.


1 2 3 28