Story #5050
As a user, I can upload a collection to the one-shot uploader
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
API Bindings, Documentation
Sprint:
Sprint 55
Quarter:
Description
Related issues
Associated revisions
History
#1
Updated by daviddavis over 1 year ago
Where do the collection fields (namespace, name, version) come from? Also, how will we use the same collection import task code? copy+paste it?
#2
Updated by bmbouter over 1 year ago
The import_collection code opens up the tarball. The import collection code is the RQ task that already exists in Pulp.
https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/galaxy/tasks.py#L15-L41
#3
Updated by daviddavis over 1 year ago
- Groomed changed from No to Yes
- Sprint set to Sprint 55
#4
Updated by bmbouter over 1 year ago
- Status changed from NEW to POST
- Assignee set to bmbouter
#5
Updated by bmbouter over 1 year ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp_ansible|e5963cce277cc1bc9ac59c2bd27f373fd624fcff.
#6
Updated by kersom over 1 year ago
- Related to Test #5268: Test - As a user, I can upload a collection to the one-shot uploader added
Please register to edit this issue
Added Collection One Shot Uploader
The import_collection task was used by the Galaxy API to receive an artifact from mazer, but this reuses it for a new viewset in the Django API.
https://pulp.plan.io/issues/5050 closes #5050