-
Notifications
You must be signed in to change notification settings - Fork 265
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
Add support for array parameters in the Create TaskRun and Create PipelineRun pages #2171
Comments
Thanks for opening this issue @torrescd. I'm converting it to a feature request since it's not something we've supported in any Dashboard release so far but would be a good addition. There are a number of ways we could present this in the Create PipelineRun / TaskRun UI.
Do you have any thoughts on how you would expect to be able to enter them? Can you provide some examples of how you're using array parameters in your Tasks? |
Thank you for consider the request. Maybe another possibility to process the array value always as a yaml array, able to be parsed. e.g.
Currently, when the default value is displayed is showing a comma-separated list, but is not able to be parsed if you enter a new list, maybe this list format working is another option. Regards! |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
We still want this, freezing so it doesn't get auto-closed. |
This is currently supported on the Create PipelineRun page via the recently added YAML mode. It would still be great to have this functionality in the form-based UI too for ease of use so keeping the issue open. |
/area roadmap |
Is your feature request related to a problem ?
Imposible to enter/change an array parameter through UI.
All input changes seems to be transformed to string. (Default untouched arrays work well)
Describe the solution you'd like
Some way to enter/change an array parameter
Describe alternatives you've considered
Additional context
Steps to see current behaviour (array parameters converted to string)
The text was updated successfully, but these errors were encountered: