StackStorm / StackStorm/st2

Allow passing in expressions in to do: in orquesta

Open
#4,576 7 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

SUMMARY

We use a lot of human assisted workflows and we really need the ability to dynamically pass in the next action to be performed in a do: block.

for example

post_check_failed:
    action: core.ask
         input:
           schema:
             type: object
             properties:
                retry:
                  type: boolean
                  required: True
                bypass:
                  type: boolean
                  required: True
          next:
            - when: <%  task(post_check_failed).result.response.retry = true %>
              do : perform_post_checks
            - when: <%  task(post_check_failed).result.response.bypass = true %>
              do: disable_module_locators
            - when: <% task(post_check_failed).result.response.bypass = false and task(post_check_failed).result.response.retry = false %>
              do: perform_post_checks

I need to repeat this pattern for each task I want to retry like this. This makes my workflows 2x as long harder to manage and fragile.

Essentially after a task fails i want to be able to go to an inquiry that asks the user if they want to retry task that just failed or if they want to bypass to next step:

so: do: pause_retry: "action to retry" , "next action upon bypass"

ISSUE TYPE
  • Feature Idea

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

The issue describes dynamic expressions in Orquesta do: blocks and a pause/retry workflow, but names no files, tests, or implementation entry points. Start by locating the Orquesta workflow execution and expression-evaluation code, then define tests covering retry and bypass choices; done means the requested dynamic next-action behavior is specified and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.