Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Lint fails to report a Name which is over 63 characters long #5318

Closed
bryanrideshark opened this issue Mar 7, 2021 · 0 comments · Fixed by #5324
Closed

Lint fails to report a Name which is over 63 characters long #5318

bryanrideshark opened this issue Mar 7, 2021 · 0 comments · Fixed by #5324
Assignees
@simster7
Labels
type/bug

Comments

@bryanrideshark
Copy link

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@simster7 simster7

Labels
type/bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Disallow object names with more than 63 chars simster7/argo
2 participants
@simster7 @bryanrideshark