[Pulp-list] sync entire puppet repo
mhrivnak at redhat.com
Wed Aug 28 14:22:17 UTC 2013
That does seem to be the default and only behavior possible. Would you mind filing a bug on this? I think we have just enough time to get something in place for Pulp 2.3.
----- Original Message -----
From: "Hawk Newton" <hnewton at constantcontact.com>
To: pulp-list at redhat.com
Sent: Tuesday, August 27, 2013 1:44:37 PM
Subject: [Pulp-list] sync entire puppet repo
I've been looking at pulp to act as a local puppet module repository to both mirror puppet forge and host proprietary private modules.
I've followed the steps outlined here: https://pulp-puppet-user-guide.readthedocs.org/en/pulp-2.1/quick-start.html#create-a-repository ... After running the sync it appears that only the most recent versions of modules in the public repository were sync'd, and while I can certainly understand the desire to keep the footprint down, this means that installation of a module that depends on any version of another module that is not the latest version will fail.
Is there a way to sync the entire contents of a remote repository and not just the latest versions? Am I missing something?
Pulp-list mailing list
Pulp-list at redhat.com
More information about the Pulp-list