We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened/what you expected to happen?
When you hard-code a name for your workflow, if the length is over 63 characters the entire thing dies on the vine.
name
Rookie mistake on my part, but it would be nice if Lint would error out in these circumstances.
Lint should prevent users from submitting a broken workflow.
What Kubernetes provider are you using?
Microk8s
What version of Argo Workflows are you running?
v2.12.8
Reproduction is simple - just create a workflow which has a name longer than 63 characters and things will blow up.
The text was updated successfully, but these errors were encountered:
simster7
Successfully merging a pull request may close this issue.
Summary
What happened/what you expected to happen?
When you hard-code a
name
for your workflow, if the length is over 63 characters the entire thing dies on the vine.Rookie mistake on my part, but it would be nice if Lint would error out in these circumstances.
Lint should prevent users from submitting a broken workflow.
Diagnostics
What Kubernetes provider are you using?
Microk8s
What version of Argo Workflows are you running?
v2.12.8
Explanation
Reproduction is simple - just create a workflow which has a name longer than 63 characters and things will blow up.
The text was updated successfully, but these errors were encountered: