You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose a feature request for Argo Workflows. Currently, when a WorkflowStep needs to reference a template in a WorkflowTemplate, it must specify the template name explicitly using templateRef. This request is to allow a WorkflowStep to call the entrypoint of a WorkflowTemplate directly without needing to specify the template name.
Motivation
In many use cases, it is beneficial to call the entrypoint of a WorkflowTemplate from a WorkflowStep, especially in scenarios where the WorkflowTemplate is designed with a primary entrypoint that is commonly used. Having to specify the template name explicitly in each WorkflowStep can be redundant and less flexible, particularly if the WorkflowTemplate's entrypoint changes over time.
Suggested Implementation
An approach could be making template property optional, or introducing a new field or a special syntax used in combination of templateRef field that, which would automatically refer to the entrypoint of the specified WorkflowTemplate.
The text was updated successfully, but these errors were encountered:
agilgur5
changed the title
Allow WorkflowStep to Call Entrypoint of WorkflowTemplate
Allow templateRef for Entrypoint without requiring nameApr 4, 2024
Summary
I would like to propose a feature request for Argo Workflows. Currently, when a WorkflowStep needs to reference a template in a WorkflowTemplate, it must specify the template name explicitly using
templateRef
. This request is to allow a WorkflowStep to call the entrypoint of a WorkflowTemplate directly without needing to specify the template name.Motivation
In many use cases, it is beneficial to call the entrypoint of a WorkflowTemplate from a WorkflowStep, especially in scenarios where the WorkflowTemplate is designed with a primary entrypoint that is commonly used. Having to specify the template name explicitly in each WorkflowStep can be redundant and less flexible, particularly if the WorkflowTemplate's entrypoint changes over time.
Suggested Implementation
An approach could be making template property optional, or introducing a new field or a special syntax used in combination of
templateRef
field that, which would automatically refer to the entrypoint of the specified WorkflowTemplate.The text was updated successfully, but these errors were encountered: