StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html
When I run this, I get some strange behavior. Only the first two tasks run - both successfully. Yet, the workflow exits after those two and reports a failure.
I then noticed the fork argument isn't defined in st2cd.st2_prep_release_ci_rules. However, I have two concerns:
Why did the workflow exit without even attempting to describe the error?
An error describing an invalid YAQL expression isn't really the real problem. While it's true that $.fork doesn't exist, and that would result in an invalid YAQL expression, I'm using an argument that isn't defined in the action metadata. I imagine this is an order-of-processing issue, so it's possible this can't get fixed without changing mistral, so we should at a minimum address the last comment about displaying an error at all
I am troubleshooting one of the CD workflows, and currently it's in this state:
When I run this, I get some strange behavior. Only the first two tasks run - both successfully. Yet, the workflow exits after those two and reports a failure.
I suspected mistral could tell me more, so I looked at the latest execution:
I then noticed the
fork
argument isn't defined inst2cd.st2_prep_release_ci_rules
. However, I have two concerns:$.fork
doesn't exist, and that would result in an invalid YAQL expression, I'm using an argument that isn't defined in the action metadata. I imagine this is an order-of-processing issue, so it's possible this can't get fixed without changing mistral, so we should at a minimum address the last comment about displaying an error at all