Actions
Story #5165
closedAs a user, I can mirror collection content
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 57
Quarter:
Description
Currently pulp_ansible calls out to Mazer to perform the sync of Collection content from the Galaxy V2 API. This was done initially to get something working, but it's inefficient since the Stages API could provide asyncio based downloading and Artifact creation.
Solution¶
Switch pulp_ansible sync to use the Stages API instead. This will require several calls to be made to implement the client side of the Collection downloading workflow.
The calls that will need to be made by the downloaders will need to probably call the V2 collection URLs pulp_ansible implements here: https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/urls.py#L24-L38 Also the /api/
call.
Actions
Sync collections with stages API
Sync all collections (a full mirror) from Galaxy. Removing whitelist from CollectionRemote, now you can sync collections utilizing just the url:
closes #5165 https://pulp.plan.io/issues/5165