metadata.generateName or metadata.name should allow variables in their definition

[tooptoop4]

if I try some variable within these values they complain about { is not a valid alphanumeric

[terrytangyuan]

I don’t think you can substitute these.

[alexec]

This is not possible when submiting a Workflow directly, because the name must be know at submission time.

But what about WorkflowTemplate? We could do something like this:

kind: WorkflowTemplate
spec:
  workflowMetadata:
    name: 
     valueFrom: 
       expression: "my-expression"

[tooptoop4]

@alexec does your example work in released version or is it a proposal?

[alexec]

It is proposal.

[tooptoop4]

any workarounds? as workflow that runs often is getting name collisions so it can't be archived

[raven-wing]

there is workaround:

            - src:
                dependencyName: test-dep
                dataTemplate: "{{ .Input.body.pull_request.number }}-{{ .Input.body.pull_request.head.sha | substr 0 7 }}"
              dest: metadata.name

from here

[tooptoop4]

@raven-wing that is only for argo-events objects?

[agilgur5]

there is workaround:

You can also use the Workflow of Workflows pattern with a wrapper Workflow to do something similar. That's potentially the easiest way to do it with Argo Workflows alone (i.e. without Events etc).

Otherwise this isn't possible to do directly, as mentioned above

[tooptoop4]

i think longer randomized string + timestamp (for wftemplate and cronwf) is most important when submitted via ui since it has no option to append