-
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
feat: set template display name in yaml #14077
Conversation
Signed-off-by: MenD32 <[email protected]>
Signed-off-by: MenD32 <[email protected]>
b367fde
to
000a881
Compare
Signed-off-by: MenD32 <[email protected]>
c136f29
to
1193701
Compare
Signed-off-by: MenD32 <[email protected]>
1193701
to
83db9ba
Compare
Signed-off-by: MenD32 <[email protected]>
…rkflows into feat/template-displayname Signed-off-by: MenD32 <[email protected]>
Could you post some screen shots? |
examples/loops-param-argument.yaml
Outdated
@@ -34,6 +34,7 @@ spec: | |||
withParam: "{{inputs.parameters.os-list}}" | |||
|
|||
- name: cat-os-release | |||
displayName: "os-{{inputs.parameters.image}}-{{inputs.parameters.tag}}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we refer to kubeflow pipeline to implement it with annotations?
https://github.com/kubeflow/pipelines/pull/2459/files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah sure
now looks like this:
annotations:
workflows.argoproj.io/display-name: "os-{{inputs.parameters.image}}-{{inputs.parameters.tag}}"
Signed-off-by: MenD32 <[email protected]>
Signed-off-by: MenD32 <[email protected]>
e362891
to
696a7a8
Compare
Signed-off-by: MenD32 <[email protected]>
This feature can be used more widely than loops, to add pretty names for any node? I think this should be documented in markdown properly, rather than just in an example for one feature (loops). The "Annotations" part of the feature feels obscure as it is - what does it actually do to my pods for the different template types? And then document the special annotation that you've added here. |
it can be used for any node, not specifically in loops, I'll add a new page in the docs to document this. |
Signed-off-by: MenD32 <[email protected]>
Signed-off-by: MenD32 <[email protected]>
Signed-off-by: MenD32 <[email protected]>
is the docs CI broken? looks like its failing spellcheck on unchanged docs... |
Signed-off-by: MenD32 <[email protected]>
Signed-off-by: MenD32 <[email protected]>
Signed-off-by: MenD32 <[email protected]>
34d1600
to
675d698
Compare
Signed-off-by: MenD32 <[email protected]>
675d698
to
6fdef4d
Compare
Signed-off-by: MenD32 <[email protected]>
e802a10
to
2dacf13
Compare
Signed-off-by: MenD32 <[email protected]>
2dacf13
to
5951b1e
Compare
Signed-off-by: MenD32 <[email protected]> Co-authored-by: MenD32 <[email protected]> Signed-off-by: Alex Collins <[email protected]>
Feature: set up custom names for displayName in template definition
suggested on #13886
Motivation
Customizable display names for workflow nodes in the Argo UI enhance usability by allowing users to assign intuitive, context-specific labels, improving workflow readability and navigation.
This is especially prevalent in loops.
Modifications
Added displayName field to template struct, allowing to override the default displayName.
Verification
e2e test - loops-param-argument.yaml