December 8, 2015
by Manas Kelshikar
The holidays are upon us and we decided to celebrate with our v1.2.0 release of StackStorm! StackStorm v1.2.0 follows up as an update to our blockbuster v1.1.0.
StackStorm 1.2 features significant changes to ChatOps, some smaller improvements and plenty of bug fixes. Lets walk through some of the highlights –
The ChatOps changes are so extensive that we decided to dedicate a separate blog here. Once users familiarized themselves with StackStorm-powered ChatOps we received excellent feedback which has been translated into some of the improvements in this release.
The major theme is extending further your control of your ChatOps and especially what is presented in your precious chat real-estate. We commercially support ChatOps – and we think improve it greatly versus rolling your own flavor of a bot or directly connecting more and more integrations to chat.
While we were at it we also took the liberty of reworking some StackStorm internals to better suit ChatOps needs thus enabling some of the features and opening up the door for many more future improvements.
StackStorm remote runners now support bastion hosts. If your infrastructure requires bastion hosts to access various parts of the infra then we have you covered. Simply specify the bastion host property to proxy commands over to a remote host.
We love it when community members contribute key features and help to grow StackStorm. Your contributions are welcome and much appreciated. Thank you Logan!
You must already know about StackStorm Packs. Take a look at our community StackStorm Exchange for a wide range of existing packs.
With v1.2.0 we worked to improve the ability to test packs so that packs can get the same rigorous unit testing and integration testing as you would for your applications. These improvements make it easier to manage packs with a CI/CD pipeline so that you can make sure that only quality packs show up in a production StackStorm installation – this is DevOps getting a little meta. Infrastructure as code!
Check out the pack testing docs to learn more.
Notifications used to only be static strings. As we strive to provide users more control, we decided to make it so that notifications can now be templatized. This means the notification messages can be more meaningful and fit better into your approach.
Notifications are a convenient way for StackStorm to either email, text, or respond in chat on the completion of an execution – or maybe you can invent another way to use them. More info about notifications can be found here.
Timeouts are a fact of our modern day Ops life. So we decided to provide these some special meaning and also this allowed us to enable some interesting policies. You can now setup a policy to retry N times on a timeout since often timeout failures resolve on a retry. Docs for retry policy can be found here.
StackStorm 1.2 also adds more validation and better error reporting for the simple ActionChain workflow engine. Here we are trying to better report any statically identifiable errors and also to provide visibility into failures.
This is a no-op action that can be used as a placeholder action while testing workflows and rules and so forth. Also, this core.noop action is tremendously useful when combined with notifications and other value adds on top of an execution.
Previously, StackStorm deployments required separate ports to serve AUTH and API endpoints (9100 and 9101). We changed this to enable StackStorm to serve all the REST API endpoints off a single HTTPS, and made them “default” when you deploy StackStorm with All-in-one installer.
But wait, there is more! To see the full list features and bug fixes new in v1.2.0 head over to the release notes.
As always if you got question or would just like to say hi please head over to https://stackstorm.com/community/ on how to find us.