StackStorm / StackStorm/st2

Orquesta should allow publishing of all the intermediate task results and published variables

Open
#4,532 9 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature workflows: orquesta
Dominant language
Python
Stars
6.5k
Forks
787
PR merge metrics
No merged PRs in 30d

Description

Right now Orquesta doesn't include intermediate task results and published variables in the result attribute and st2 execution get <id> -d command output which makes developing and debugging Orquesta workflows slow and not fun.

In action-chain and mistral-v2 runner we already have display_published runner level parameter which makes it include published variables in the result output.

In addition to that, Mistral already includes all that info in result attribute. The problem with Mistral is that it's too noisy so we should find some kind of balance (aka only publish task results and variables when some runner parameter is set or similar).

NOTE: I created this issue on this repo and not StackStorm/orquesta, because I believe that's primary a feature of the Orquesta StackStorm runner. If we will need additional features and / or changes in orquesta repo, we can open corresponding issues there as well.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the Orquesta runner behavior with the existing action-chain and mistral-v2 runner handling of display_published, then inspect how result is exposed through st2 execution get -d. Done means intermediate task results and published variables can be included through a configurable runner option without making output as noisy as Mistral.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.