Story #7621
closedAs a user, I can copy content from one repository to another
100%
Description
Problem¶
The current repository modify endpoint[0][1] calls the add_remove task[2] which just adds or removes content to a repository. For users copying content between repos, this has been sufficient up until now as content is fully self contained. The problem though is with #7504 we are storing deprecated information per repository. So when content is copied over using the modify endpoint and add_remove task, that information is not being copied.
Solution¶
Add a copy endpoint similar to the one in pulp_rpm[3]. This endpoint tasks a source repository version, a destination repository, and a set of content to be copied. It calls a new task (copy_content?) with these parameters and copies over the content plus any repository data (ie AnsibleCollectionDeprecated).
Related issues
Updated by daviddavis almost 4 years ago
- Related to Issue #7504: Set deprecated status on synced collections. added
Updated by fao89 almost 4 years ago
- Related to Story #7670: [EPIC] As a Galaxy V3 api user, I can sync repository metadata added
Updated by bmbouter almost 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
Updated by bmbouter almost 4 years ago
- Has duplicate Story #7749: As a user, I can copy collectionVersions from one repo to another added
Added by bmbouter almost 4 years ago
Updated by bmbouter almost 4 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp_ansible|69b5c96613ebc6aa3333cc6c6cdadf28853e8943.
Updated by pulpbot almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Adds copy endpoint and task
closes #7621