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

UI for providing input parameters to a (templated) workflow #1999

Closed
nicorikken opened this issue Jan 16, 2020 · 2 comments · Fixed by #2030
Closed

UI for providing input parameters to a (templated) workflow #1999

nicorikken opened this issue Jan 16, 2020 · 2 comments · Fixed by #2030
Assignees
Labels
type/feature Feature request

Comments

@nicorikken
Copy link

nicorikken commented Jan 16, 2020

Summary

The main reason we are considering Kubeflow is the UI which has a user-friendly way of providing run parameters. With the arrival of WorkflowTemplates in v2.5 it seems that Argo is close to a similar user-experience and I think it might be worthwhile to have a similar feature in 'plain' Argo Workflow.

Motivation

We use Argo Workflow for simulations and machine learning. Experimenting with different parameters is important part of the user-experience as they want to test different scenario's. The workflow structure itself hardly changes, but the parameters do. Also the users are data-scientists which can deal with inserting YAML, but would prefer neat fields.

Proposal

In addition to the 'insert-yaml-here' way of submitting a workflow or definitions, provide a user-friendly way to provide parameters. Something like Kubeflow is offering:

image

ArgoCD already provides such an interface, which takes the defaults from a YAML file. A similar approach can be used:

Screenshot from 2020-01-16 09-37-54

ArgoCD even shows an emergency icon if the default value has been changed, for clarity:

Screenshot from 2020-01-16 09-41-08

And is has the option to remove such an override easily. That might be convenient in Argo Workflow when a workflow is replayed:

Screenshot from 2020-01-16 09-43-58


Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@nicorikken nicorikken added the type/feature Feature request label Jan 16, 2020
@simster7 simster7 self-assigned this Jan 16, 2020
@simster7
Copy link
Member

I'll work on a PoC of this today

@nicorikken
Copy link
Author

@simster7 thanks. I'm looking forward to this feature!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature Feature request
Projects
None yet
2 participants