-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generateName
or name
should allow variables in their definition
#7900
Comments
I don’t think you can substitute these. |
This is not possible when submiting a But what about kind: WorkflowTemplate
spec:
workflowMetadata:
name:
valueFrom:
expression: "my-expression" |
@alexec does your example work in released version or is it a proposal? |
It is proposal. |
any workarounds? as workflow that runs often is getting name collisions so it can't be archived |
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 |
@raven-wing that is only for argo-events objects? |
generateName
or name
should allow variables in their definition
You can also use the Workflow of Workflows pattern with a wrapper Workflow to do something similar. Otherwise this isn't possible to do directly, as mentioned above |
if I try some variable within these values they complain about
{ is not a valid alphanumeric
The text was updated successfully, but these errors were encountered: