I've got multiple repos assigned to a content view … most are updated
frequently - however I only want to use those updates once every six weeks
(most do not contain errata) as that is my patching cycle.
On the odd occasion we want to use some updates which have been synced, and
push those through our environments.
How can I do that without pushing through all the updates from the other
ie … how can i selectively push through changes to one repository whilst
ignoring the rest … or even just one rpm if neccessary.
----- Original Message -----
> From: "AJ"
> To: email@example.com
> Sent: Friday, September 26, 2014 7:21:48 PM
> Subject: [foreman-dev] [katello 1.4] Content View question
> Just a quick question (hopefully!)
> I've got multiple repos assigned to a content view .. most are updated
> frequently - however I only want to use those updates once every six weeks
> (most do not contain errata) as that is my patching cycle.
> On the odd occasion we want to use some updates which have been synced, and
> push those through our environments.
> How can I do that without pushing through all the updates from the other
> repositories too?
> ie .. how can i selectively push through changes to one repository whilst
> ignoring the rest .. or even just one rpm if neccessary.
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to firstname.lastname@example.org.
> For more options, visit https://groups.google.com/d/optout.
Thanks for that, it seems this is the feature I will miss most about v1.2
then going forwards.
Would it be worth me raising this with the pulp team, as in 1.2 version of
pulp I was able to inject an rpm into a repository, in the version of pulp
used for Katello 1.4 this errors.
I know this breaks Katello's storage of packages, but I was thinking of
something like this …
Create a repository for emergency patches (for instance the bash
vulnerability), assign it to the content views.
use the pulp-admin command to inject the new patch and its dependencies
directly in the pulp repo associated with the environment and content view.
If we were to do this in Katello, it would be to modify the content_upload
cli command to work with environments other than Library, ie as seem in the
hammer context for other commands as --environment Develop/content_view