Project

Profile

Help

Story #5334

As a user, I can immediately download Collection content after uploading it

Added by bmbouter 3 months ago. Updated 3 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

The UploadCollection is available in 3 places in pulp_ansible:

  • In the /pulp/api/v3/ viewset area here
  • In the Galaxy V2 API here
  • In the Galaxy V3 API here

In the Galaxy V2 and Galaxy V3 areas, the viewset knows specifically which Distribution that client is accessing the Galaxy API through.

Design

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.

Associated revisions

Revision a662fc2c View on GitHub
Added by bmbouter 3 months ago

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
are created).

https://pulp.plan.io/issues/5334
closes #5334

History

#1 Updated by bmbouter 3 months ago

  • 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.

#2 Updated by bmbouter 3 months ago

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.

#3 Updated by bmbouter 3 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bmbouter

#4 Updated by bmbouter 3 months ago

  • Status changed from ASSIGNED to POST

#5 Updated by bmbouter 3 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF