As a user, I can immediately download Collection content after uploading it
The UploadCollection is available in 3 places in pulp_ansible:
In the Galaxy V2 and Galaxy V3 areas, the viewset knows specifically which Distribution that client is accessing the Galaxy API through.
For the Galaxy V2 and V3 APIs, the viewset knows the Distribution the client is uploading to. For those two APIs any new Collection content should create and be associated with a new RepositoryVersion. This should only create a RepositoryVersion if the Distribution.repository is set because that will cause the RepositoryVersion to be served automatically.
Auto create RepoVersion on Collection Upload
The Galaxy V2 and V3 APIs are accessed through a specific
AnsibleDistribution. If that AnsibleDistribution is related to a
Repository, an upload will create a new RepositoryVersion.
Note: if the AnsibleDsitribution is serving a specific RepositoryVersion
(not "the latest" from a Repository), no additional RepositoryVersions
- Subject changed from As a user uploading a Collection through a "distribution", a new RepositoryVersion is created for the associated Repository to As a user, I can immediately download Collection content after uploading it
I retitled it to reflect the actual goal.
My first instinct is that there are already add/remove calls in core that allow the user to facilitate this with 1 extra call. When pulp_ansible is the Collection storage backend for Galaxy that is fine, but what about cases where the `ansible-galaxy collecitons` CLI is being used with pulp_ansible directly? The CLI won't know to make those extra calls.
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp_ansible|a662fc2cf15d171a07dd7dd699291e373b9b0a9a.
Please register to edit this issue