Project

Profile

Help

Issue #5417

Content upload with repo association should also lock the repository

Added by mdellweg about 2 years ago. Updated about 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Whenever a repository is mentioned in the content upload endpoint, a new repository version is to be created. Therefore the viewset must add the repository to the locked resourced on that condition.

Example code: https://github.com/pulp/pulp_deb/blob/ef45f773d664e688420df440ecc1b1b6cc7f9eeb/pulp_deb/app/viewsets.py#L169


Related issues

Copied to Python Support - Issue #5418: Content upload with repo association should also lock the repositoryCLOSED - NOTABUG<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by mdellweg about 2 years ago

  • Copied to Issue #5418: Content upload with repo association should also lock the repository added

#2 Updated by ttereshc about 2 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 58

#3 Updated by rchan about 2 years ago

  • Sprint deleted (Sprint 58)

#4 Updated by fao89 about 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89

#5 Updated by fao89 about 2 years ago

  • Status changed from ASSIGNED to CLOSED - WONTFIX

It was solved by adopting SingleArtifactContentUploadViewSet on #5453

#6 Updated by fao89 about 2 years ago

  • Assignee deleted (fao89)

Please register to edit this issue

Also available in: Atom PDF