Is there a way to pass in a string param to a flow where the string contains

{{ }}

? I have a coworkers who is writing a flow that involves calling an LLM. One of the parameters is a big prompt string which contains

{{ "key_1": "example_val_1", "key_2",,, }}

. when he runs the flow with Argo he gets an error

bash: key_1: command not found

. In Argo I can see the manifest has

--system-instructions={{workflow.parameters.system-instructions}}

, and in GKE I can see the command executed in the contains has the string substituted. The string substitution looks like it’s done correctly in the GKE command, but things go haywire when the command is run. What’s the solution here? Should we escape these brackets?

Interesting - we can look into addressing this issue in the implementation. Have you tried out the escaping approach?

haven’t yet - I’ll ask my colleague to give it a try and see what happens