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.

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

Merged
merged 1 commit into from Oct 9, 2019
Merged

Helpful error message when multiple volumes share name #1404

merged 1 commit into from Oct 9, 2019

Conversation

ghost
Copy link

@ghost ghost commented Oct 9, 2019

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:

Release Notes

The error message emitted when a Task has multiple volumes with the same name has changed to describe the conflict more clearly.

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.
@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Oct 9, 2019
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 9, 2019
@tekton-robot
Copy link
Collaborator

The following is the coverage report on pkg/.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/pipeline/v1alpha1/task_validation.go 77.1% 79.9% 2.8

imjasonh added a commit to imjasonh/pipeline that referenced this pull request Oct 9, 2019
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"
Copy link
Member

@dibyom dibyom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 9, 2019
@tekton-robot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 9, 2019
@tekton-robot tekton-robot merged commit 5824fd5 into tektoncd:master Oct 9, 2019
imjasonh added a commit to imjasonh/pipeline that referenced this pull request Nov 15, 2019
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"
imjasonh added a commit to imjasonh/pipeline that referenced this pull request Nov 15, 2019
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"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Confusing error when same volume name used twice
3 participants