In https://github.com/knative/build-pipeline/blob/8a2b6c30efa7f4dd1fedafacc2733a0d290e12c6/examples/deploy_tasks.yaml#L21, the Input Param helmArgs is used. If one were to set helmArgs to be --set arg1=a --set arg2=b with the intention of providing multiple arguments to helm, this task would fail due to --set arg1=a --set arg2=b being interpreted as a single argument.

A couple questions that comes to mind:

1. How do we make it obvious that '${helmArgs}' could possibly be expanded to multiple arguments, while also allowing it to have a single argument? The spread operator may be a nice fit: ${helmArgs...}

2.How should a TaskParam represent an array? Currently it just has a name field, but description and default will be added soon. How does it look supporting defaults for an array alongside a regular string?