Project

Profile

Help

Issue #5418

Content upload with repo association should also lock the repository

Added by mdellweg about 1 month ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Severity:
2. Medium
Version - Python:
Platform Release:
Blocks Release:
Target Release - Python:
OS:
Backwards Incompatible:
No
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

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 repository NEW Actions

History

#1 Updated by mdellweg about 1 month ago

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

Please register to edit this issue

Also available in: Atom PDF