Project

Profile

Help

Issue #5418

closed

Content upload with repo association should also lock the repository

Added by mdellweg over 4 years ago. Updated almost 4 years ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Python:
Platform Release:
Target Release - Python:
OS:
Triaged:
No
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

see also: https://pulp.plan.io/projects/pulp_rpm/issues/5417


Related issues

Copied from RPM Support - Issue #5417: Content upload with repo association should also lock the repositoryCLOSED - WONTFIXActions
Actions #1

Updated by mdellweg over 4 years ago

  • Copied from Issue #5417: Content upload with repo association should also lock the repository added
Actions #2

Updated by dalley almost 4 years ago

  • Status changed from NEW to CLOSED - NOTABUG

Also available in: Atom PDF