I don't have any existing tooling, but this sounds related to a migration idea that came up recently...
For migration from Pulp2 -> Pulp3 specifically, I think having a Pulp2 feature that outputs a config of all Pulp2 repositories for example. Then the user could edit this config file which would be declaring how to handle/replicate that repo into your Pulp3 install by editing the template. The migration tool would validate and consume this template. FYI the Pulp2 -> Pulp3 epic in Redmine is here https://pulp.plan.io/issues/3821 I haven't put this idea into that yet (and I should). On Mon, Apr 8, 2019 at 11:04 AM Kodiak Firesmith <[email protected]> wrote: > Hello Pulp-List! > > I've frequently found myself in need of propagating various in-Pulp > settings out to other Pulp servers without doing a full database > dump/restore. Examples might be dumping a set of organizations from my > main server and loading them into a test host. I have not yet written > something like this do do the work more easily. I figured before digging > any deeper that I'd reach out to the list to see if someone else might have > already done the hard work, especially as I see this being useful for > potentially dumping configs from Pulp 2.x in preparation for moving to Pulp > 3.0, though understandably those configs won't be 1:1 by any stretch, but > if dumps could be done into a common format like YAML, perhaps a new load > tool for Pulp 3.x could translate those into Pulp 3x API. > > Thanks! > - Kodiak > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
