Anton Gilgur

I took a quick look since the CLI is pretty small. It looks like my initial thought process was partly correct actually, that flag is [inherited from `kubectl`](https://github.com/argoproj/argo-workflows/blob/b6d6403320157e614af2c14c2417433e55eadec1/cmd/argo/commands/client/conn.go#L31) and so...

We can just re-use this issue as a feature request. It's somewhere in between a bug and a feature as I can understand why you would be confused that the...

> We currently support multiple templating/expression engines without any strong reason. Legacy and backward-compat is the main reason at this point. Each templating engine was superior to the prior historically...

> I don't see a huge issue here If I am being honest, simplicity is why I proposed this Completely off the top of my head, escaping sounds like a...

> Is `$env` interferers somehow with Argo defined variables? No, not currently, but Isitha was suggesting here to change Argo's `{{=` `}}` to use `$` instead, which could create overlap....

I discussed this with Isitha in the [Aug 20th Contributor Meeting](https://docs.google.com/document/d/1tznN5LB-KrNkC6dmeIzpKfuyvZWgCJpRuS-E84zseC8/edit#heading=h.jh0wp5re8e6) and pointed to my [above comment](https://github.com/argoproj/argo-workflows/issues/13471#issuecomment-2290597375) on how the `$` syntax would not suffice. Isitha also agreed that we...

> Another problem with `$` is it conflicts with shell scripts. It's common to use templating with shell code, e.g.: Well we should probably disable templating inside of scripts in...

This was superseded by #13495, which had the proper changes by the assignee

@Joibel could you please re-format your PR descriptions? I think they're line-breaking at 80 chars or something, which depending on the width of the GH description, can sometimes cause a...

> The bulk of this PR is necessary to make that case work, and I'd consider it too invasive to backport. Gotcha. Yea when I examined the issue it could...