Actions
Issue #5417
closedContent upload with repo association should also lock the repository
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
Updated by mdellweg over 4 years ago
- Copied to Issue #5418: Content upload with repo association should also lock the repository added
Updated by ttereshc over 4 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 58
Updated by fao89 over 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to fao89
Updated by fao89 over 4 years ago
- Status changed from ASSIGNED to CLOSED - WONTFIX
It was solved by adopting SingleArtifactContentUploadViewSet on #5453
Actions