-
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
invalid container names (i.e. not "main") are allowed and causes bugs #6405
Labels
Milestone
Comments
alexec
changed the title
invalid container names (i.e. not "main") are allow and causes bugs
invalid container names (i.e. not "main") are allowed and causes bugs
Jul 22, 2021
@alexec with pleasure ! |
I think basically if you validate a workflow, and the container is not named "main", there should be an error. |
This is actually a regression. |
alexec
added
the
type/regression
Regression from previous behavior (a specific type of bug)
label
Jul 22, 2021
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Jul 22, 2021
…ixes argoproj#6405 Signed-off-by: Alex Collins <alex_collins@intuit.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We should not allow invalid container names. It is confusing for users and costs time to investigate.
I think we can add a check here:
argo-workflows/workflow/validate/validate.go
Line 372 in 092b427
@stevenbressey would you be interested in helping fix this as you were impacted by this recently?
The text was updated successfully, but these errors were encountered: