Hey I noticed there is an ArgoClient provided by the metaflow team for submitting argo workflows. Now, the issue for me is how the parameters are used by metaflow-originated argo workflows as opposed to native argo workflows. --- What I am trying to pass to is a

string

. This string is a comma separated list of string which will splitted based on

,

by the flow (exact same method used) The method simply does:

out_list = [out.rstrip().lstrip() for out in input_string.split(delimeter)]
    return out_list

--- Now, I have two flows: 1. A metaflow flow that has been converted to an argo workflow e.g

python parameter_flow.py --with retry argo-workflows create

. When using the argo client to submit the workflow with

parameters = {"comma_sep_list_of_strings": "string1,string2"}

the application is successfully splitting this into a list 2. In contrast. when submitting the native argo workflow with the same parameter

parameters = {"comma_sep_list_of_strings": "string1,string2"}

, the list will end up being

['"string1', 'string2"']

• The default value for this

comma_sep_list_of_strings

parameter in both cases is

""

• (Json file) The representation of the default value for the parameter by the metaflow created argo workflow is

"\"\""

• (Json file) The representation of the default value for the parameter by the metaflow created argo workflow is

""

(from the ArgoUI) It should be noted that I don't have the same issue when submitting the native argo workflow from the UI. Is there anything I am missing on how to submit the native argo workflow? Thanks

Maybe @thankful-ambulance-42457 knows