Project

Profile

Help

Story #4764

As a user, I can sync a list of Collections from galaxy.

Added by bmbouter 5 months ago. Updated 4 months ago.

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

100%

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

Description

The user should be able to sync down one or more {namespace}.{name} Collections similar to what mazer installs here: https://galaxy.ansible.com/docs/mazer/examples.html#installing-repositories-with-multiple-roles

Solution

Add a CollectionRemote and give it a 'white_list' attribute. This attribute accepts the same argument value as the `mazer install` command. Specifically it accepts one or more collections separated by spaces. Each collection is specified by namespace.name and an optional version string. If version string is unspecified, the latest is downloaded. If a version string is specified, that version is downloaded.

So for example:

foo.bar,1.2.3 foo.baz,2.3.4 foo.zab

would sync down and create 3 collections:
1. foo.bar version 1.2.3 (even if newer was available)
2. foo.baz version 2.3.4 (even if newer was available)
3. foo.zab it will discover whatever the latest is and use that. Syncing without a version of time should give you newer and newer collections.

Associated revisions

Revision fc72facd View on GitHub
Added by bmbouter 4 months ago

Add mazer whitelist sync

Adds a CollectionRemote which users can use to sync a whitelist of
collections. With the sync a repsository is required and a new
respoitory version is created with the sync'd content downloaded.

If mazer downloads content that already exists it will not add
additional Artifacts or Collection units to pulp_ansible.

If sync discovers no new collections it does not create a
RepositoryVersion.

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

History

#1 Updated by bmbouter 4 months ago

  • Description updated (diff)

Adding some details into seeing how Mazer does it.

#2 Updated by bmbouter 4 months ago

  • Description updated (diff)

#3 Updated by daviddavis 4 months ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

#4 Updated by bmbouter 4 months ago

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

#5 Updated by bmbouter 4 months ago

  • Status changed from ASSIGNED to POST

#6 Updated by bmbouter 4 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