-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Helpful error message when multiple volumes share name #1404
Conversation
A Task is not allowed to have multiple volumes that share a name. Prior to this commit the error message printed when a name collision occurred was "expected exactly one, got both: name" which doesn't describe the problem clearly. After this commit the error message is updated to 'multiple volumes with same name "foo"'. A test case has been added to exercise the new message.
The following is the coverage report on pkg/.
|
Before this, if a user wanted to attach a Volume named "workspace" they'd get a confusing error message (tektoncd#1402). tektoncd#1404 improves the error message, but it would be nice to not have an error at all and just allow user-defined volumes named "workspace"
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Before this, if a user wanted to attach a Volume named "workspace" they'd get a confusing error message (tektoncd#1402). tektoncd#1404 improves the error message, but it would be nice to not have an error at all and just allow user-defined volumes named "workspace"
Before this, if a user wanted to attach a Volume named "workspace" they'd get a confusing error message (tektoncd#1402). tektoncd#1404 improves the error message, but it would be nice to not have an error at all and just allow user-defined volumes named "workspace"
Fixes #1402
Changes
A Task is not allowed to have multiple volumes that share a name. Prior to this commit the error message printed when a name collision occurred was "expected exactly one, got both: name" which doesn't describe the problem clearly.
After this commit the error message is updated to 'multiple volumes with
same name "foo"'. A test case has been added to exercise the new message.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
Includes docs (if user facing)Release Notes