-
Notifications
You must be signed in to change notification settings - Fork 788
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
address name contraction issues in argo-workflows create #2082
base: master
Are you sure you want to change the base?
Conversation
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.
an open question still remains how to handle the other argo CLI commands. f.ex. argo-workflows delete
in the case where a deployment with an old name exists. do we try to delete both old&new every time?
" To comply with new naming restrictions on Argo " | ||
"Workflows, this deployment replaced the\npreviously " | ||
"deployed workflow {v1_workflow_name}.\n".format( | ||
v1_workflow_name=obj._v1_workflow_name |
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.
we could also check whether v1_workflow_name
exists or not, and cut this alert out if we did not replace an old deployment
# TODO: We can create better names that try to preserve the flow name | ||
workflow_name = "%s-%s" % (workflow_name[: limit - 6], name_hash) |
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.
we could use current.flow_name
as the base and append the hash which comes from the current.project_flow_name
if the flow name is the most significant info in the template name
Though one issue with this would be that validate_run_id
relies on checking whether project/branch are part of the generated workflow_name. This needs an overhaul in any case though, as it will most likely start breaking due to the new limits
remaining items -
--name
for long names for CLI args except create