Test #5276
Test - As a user, I have simple content copy between repositories
Description
Simple content copy means that content units can be copied from one repository into another repository without considering content-type-specific invariants, such as making sure dependencies are satisfied.
The most straightforwards current design is to model this after one-shot upload. A new URL endpoint will be defined at /api/v3/rpm/copy/. POSTing to that endpoint with valid parameters will yield an asynchronous task, which will result in a new repository version in the target repository.
The user workflow should look like this:
http --form POST http://localhost:24817/pulp/api/v3/rpm/copy/ source_repository=${S_REPO_HREF} destination_repository=${D_REPO_HREF}
Both the repository parameters are required. When called, all content will be copied.
The additions to Django boilerplate will look something like this (see also: copy.py for an example of the function that does the work, and OneShotUploadSerializer in serializers.py)
urls.py
urlpatterns = [
url(r'rpm/upload/$', OneShotUploadView.as_view()),
url(r'rpm/copy/$', CopyView.as_view())
]
Related issues
History
#1
Updated by kersom over 1 year ago
- Related to Story #4716: As a user, I have simple content copy between repositories added
#2
Updated by kersom over 1 year ago
- Status changed from MODIFIED to NEW
#3
Updated by kersom over 1 year ago
- Assignee set to kersom
#4
Updated by kersom over 1 year ago
- Related to Story #5344: As a user, I have a consistant API experience for copying content added
Please register to edit this issue