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

Collection Upload doesn't raise a pretty error when uploading a duplicate Artifact. #1175

Closed
gerrod3 opened this issue Aug 17, 2022 · 0 comments · Fixed by #1176
Closed

Collection Upload doesn't raise a pretty error when uploading a duplicate Artifact. #1175

gerrod3 opened this issue Aug 17, 2022 · 0 comments · Fixed by #1176

Comments

@gerrod3
Copy link
Contributor

gerrod3 commented Aug 17, 2022

Version
0.14 and below

Describe the bug
When uploading a collection we currently don't allow duplicate files to be uploaded, so if the artifact exists it should reject the request. Currently this behavior is technically followed, but the error comes in the import task instead of at request time.

Expected behavior
400 error returned when trying to upload a duplicate collection with error message: "Artifact already exists"

Additional context
I'm going to try to unify the behavior more when I finished moving Namespace over.

gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 17, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 17, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 18, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 18, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 18, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 18, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 19, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 24, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 24, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 24, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 25, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 25, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 26, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 26, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 26, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 26, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 26, 2022
@gerrod3 gerrod3 self-assigned this Aug 26, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 29, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 29, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Aug 29, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Sep 1, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Sep 26, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Nov 17, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Nov 17, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Nov 17, 2022
gerrod3 added a commit to gerrod3/pulp_ansible that referenced this issue Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant