Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request. Output variables value assignment strategy #7105

Closed
s0rr0w opened this issue Jan 30, 2025 · 1 comment
Closed

Feature request. Output variables value assignment strategy #7105

s0rr0w opened this issue Jan 30, 2025 · 1 comment
Labels
area/backend Needs backend code changes area/frontend Needs frontend code changes enhancement New feature or request

Comments

@s0rr0w
Copy link

s0rr0w commented Jan 30, 2025

Feature description

Hi team,
It will be useful to have different strategies for output variables when task assigns the values to them, especially for repeating/loop tasks. I consider the following strategies as most needed:

  • Owerride. Default behavior. New values will override the previous ones
  • Array. New values will be stored as new array item
  • Set once. Value can be set only once.
  • Merge. Merge two objects.

It can be global parameter for tasks which doesn't have values option, and strategy can be set separately for every single key of values declaration.

Examples:

id: loop_append
namespace: demo

tasks:
  - id: loop
    type: io.kestra.plugin.core.flow.WaitFor
    condition: "{{ outputs.return.value == '4' }}"
    tasks:
      - id: kv_set_loop
        type: io.kestra.plugin.core.kv.Set
        key: test
        value: "some_value"
        kvType: STRING
        setAs: ARRAY
      - id: out
        type: io.kestra.plugin.core.output.OutputValues
        values:
          iterations: "{{ outputs.loop.iterationCount }}" as ARRAY
@s0rr0w s0rr0w added area/backend Needs backend code changes area/frontend Needs frontend code changes enhancement New feature or request labels Jan 30, 2025
@github-project-automation github-project-automation bot moved this to Backlog in Issues Jan 30, 2025
@anna-geller
Copy link
Member

This looks like an AI-generated issue. If I'm mistaken and you really have a feature suggestion, feel free to first discuss it with us in our Community Slack in the #feedback-and-requests channel.

@anna-geller anna-geller closed this as not planned Won't fix, can't repro, duplicate, stale Feb 17, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in Issues Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend Needs backend code changes area/frontend Needs frontend code changes enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

2 participants