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
It would be good to have capability of marking some actions in an integration pack as hidden so that they exist (and are used in action chains or mistral workflow tasks) but are not shown in the action list for the pack from the CLI or UI. Intention behind this is to avoid the end user directly calling these actions as their usage primarily confined from inside the workflows. Here, the workflows will be exposed to the user to execute.
Example:
In this mistral workflow, actions vslx.vslx_set_linecards and vslx.vslx_add_static_mgmt_ip are ideally not to be exposed to the end user, and should be called from the workflows only.
+1, for whatever reason the pack creator choose, some actions may not be part of the pack's UI.
And maybe add a "st2 action list --all" to be able to see the hidden ones too.
Enhancement Request:
It would be good to have capability of marking some actions in an integration pack as hidden so that they exist (and are used in action chains or mistral workflow tasks) but are not shown in the action list for the pack from the CLI or UI. Intention behind this is to avoid the end user directly calling these actions as their usage primarily confined from inside the workflows. Here, the workflows will be exposed to the user to execute.
Example:
In this mistral workflow, actions
vslx.vslx_set_linecards
andvslx.vslx_add_static_mgmt_ip
are ideally not to be exposed to the end user, and should be called from the workflows only.