Accept CSV and other files as input values for workflow

[panicboat]

Summary

The input value for WorkflowTemplate is a string, but we would also like the CSV file to be an input value.
This may be just our team, but we can work around it by opening the contents of the CSV file and copy/pasting those strings, but mistakes are often made.
Therefore, entering the file format is a safe way to execute the workflow.

Use Cases

It is often used to execute WorkflowTemplate by non-developers.

---

Message from the maintainers:

Love this enhancement proposal? Give it a 👍. We prioritize the proposals with the most 👍.

[Joibel]

With existing workflows you could pass in the CSV as a parameter (either literally or by URI) and then use that parameter in a node which extracts the relevant values for the rest of the workflow. Those extracted parameters would then be available as outputs from that node for other nodes to use.

[panicboat]

Thanks for confirming.
It seems that our organization would like to support input by file, not by CSV string or URI.
Is it difficult to put the WorkflowTemplate in the artifact-repository when it is created?

[Joibel]

I don't follow what you mean "support input by file". Can you describe what steps you're expecting to follow?

I also don't know what you mean by "Is it difficult to put the WorkflowTemplate in the artifact-repository when it is created?". This seems completely unrelated and also not something anyone would want to do. If this is a separate problem please raise a separate issue.

[panicboat]

Sorry I didn't communicate it better.

We would like to have a UI as in HTML.
I want the input to be something that specifies a file and uploads it, since opening a CSV file and copying and pasting strings is prone to errors.

[shippo-eric]

The ability to upload file object (text or binary) will be very nice! Currently, we need an async process (outside of workflows) to upload a file to s3 bucket, that makes the whole process not user friendly.