search

StackStorm / st2

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
https://stackstorm.com/
Apache License 2.0
6.05k stars 745 forks source link

Add child tasks info to orquesta workflow execution json #5073

Open sergiik opened 3 years ago

sergiik commented 3 years ago

With mistral workflows resulting execution json included all subtasks info including their statuses. It was very convenient for instance for building extended statuses for chatops output with aliases. With orquesta workflows no child info is present in resulting task json except for "children": [ ] array that contains ids only. It would be great to have extended output for subtasks for orquesta workflows similar like it was for mistral ones.

stale[bot] commented 3 years ago

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.

blag commented 3 years ago

Please fill out the issue template as we have written it.

Are you asking about how it is displayed in the web interface? or the command line interface? or something else?

Edit: More questions - what other information would you like it to show? Please be detailed and specific.

stale[bot] commented 2 years ago

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.