[Pulp-list] Ability to Sync RHUI repositories from AWS

[Ina Panova]

Hi David,

you are correct neither pulp2 or pulp3 provide this ability. Feel free to
open a feature request https://pulp.plan.io/issues/new
--------
Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."


On Wed, Jul 8, 2020 at 11:09 PM David Mora <iamperson347+public at gmail.com>
wrote:

> Hi All,
>
> I've been digging around but can't seem to find a fully supported way
> to do this in pulp2 or pulp3. What I would like to do is use pulp to
> sync the RHUI repos used in AWS to local repositories so I can create
> different repos that can be hooked to different environments (staging,
> production, etc.) within my AWS account. To connect to RHUI in AWS,
> you must specify the CA cert for the repo, entitlement cert (pub and
> key), and specify special http headers.
>
> * It appears alternate contents sources in pulp2 have support for
> headers, but this doesn't help with the initial sync of metadata
> (since the rpm plug-in repos functionality doesn't have a parameter
> for headers)
> * It appears remotes in pulp3 are in a similar situation in that they
> do not support specifying headers
>
> Is there any way to accomplish this currently with pulp2 or pulp3?
>
> Thanks,
> David
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20200721/af64d6f1/attachment.htm>