-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
dynamic template naming on workflowTemplates fails unexpectedly #14042
Comments
It is the same issue as #13773 |
Will you submit a PR to fix this issue? @MenD32 |
This bug impacts me, so if it wouldn't be fixed by someone else I'd write a fix. But it isn't my highest priority rn. |
@MenD32 , if you are working on this, please tell me, i will close my pr |
I am not working on this rn, feel free to go ahead |
reverted fix(controller): validation failed when dynamic templateRef is used in nested template #14053 due regression in #14165 |
Hi @chengjoey are you interested in continuing to work on this? |
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
templating a template name fails when using a workflowTemplate's input, this bug can be mitigated by using an intermediate template to output the input of the workflowTemplate
Version(s)
v3.6.2
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: