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
Almost all action runners have a timeout parameter (see the fancy table here), but there is no timeout parameter for Orquesta.
This means that there is no way to set a time limit a subworkflow if something goes wrong.
It would be nice to allow users to specify this parameter as a fail safe in case the Orquesta engine hangs, for example. It would also be more consistent with our other action runners:
tasks:
do_thing:
action: mypack.myworkflow # Orquesta workflow, may take awhile to finish, and/or hang
input:
timeout: 60 # seconds
Almost all action runners have a
timeout
parameter (see the fancy table here), but there is notimeout
parameter for Orquesta.This means that there is no way to set a time limit a subworkflow if something goes wrong.
It would be nice to allow users to specify this parameter as a fail safe in case the Orquesta engine hangs, for example. It would also be more consistent with our other action runners:
This has been requested by multiple people in the StackStorm Forum.