Lately I have been playing with these attributes to sync repos from private
docker registries. Question I have is if these attributes are applicable to
other content types that pulp supports like yum, puppet, ostree. Reason I
ask is I see these in the generic place
- Original Message -
| From: "Michael Hrivnak"
| To: "Bryan Kearney"
| Cc: "pulp-list"
| Sent: Wednesday, February 3, 2016 12:16:23 PM
| Subject: Re: [Pulp-list] Pulp 2.6 vs 2.8 event notifier question
|
| I'm glad we're
So katello uses pulp's http event notifiers to get information about operations
like "sync_complete". So Katello typically configures the event notifiers to
fire off to "https://localhost/katello/.; . In pulp 2.6 this used to work
ok, but with pulp 2.8 we get issues like ""
Feb 1 09:51:34
Katello has a need to mirror repositories quickly on a clone operation. To
achieve this katello uses a custom distributor for some yum based repos. This
distributor copies the metadata along with the content instead of regenerating
the metadata from scratch as is the case with a typical pulp
Here is the scenario.
I synced a repo from some feed which has packages A1, B1.
Now the feed got updated to packages A2, B1.
Now when I resync I need my repo to have A2, B1 (exact mirror). The default
behaviour in pulp seems to be not touch local repo and hence it ends up having
packages A1,
When I run the equivalent of following in 2.6
RestClient.post
"https://katello-pulp-nightly.example.com/pulp/api/v2/content/units/erratum/search/;,
"{\"criteria\":{}}", "Accept"=>"*/*; q=0.5, application/xml",
"Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"15",
I was trying to copy contents of a repo to another repo via filters based of
https://pulp-dev-guide.readthedocs.org/en/latest/rest-api/content/associate.html.
Its seems to work okay, albeit a bit confusing when dealing with dependencies
and regex cases. I was wondering if pulp had something