Add specific packges to content view

Is it possible to add only specific RPMs to existing content view and publish it.
For example, I have a content view (version 1) with some repos published today to an environment.
A month later we sync the local repos to upstream repos but we want to publish the new view (version 2) with the RPM’s of content view in Version 1 + some very specific RPMs and not include all the new RPM what were downloaded when we did the last sync.

The way we do it now is, while publishing the new view create a filter to publish only those specific RPMs but that way the new view doesn’t contain all the RPMs of the current view.

I hope I am making sense.

Expected outcome: Publish new content view that includes previous version + some new specific packages.

Foreman and Proxy versions: 2.1.2

Foreman and Proxy plugin versions:

Name Version
foreman-tasks 2.0.2
foreman_docker 5.0.0
foreman_remote_execution 3.3.7
katello 3.16.0

Distribution and version: Oracle Linux 7.9

Let me know if you need more details.
Thanks in advance.

Hi @bhatsu,

I believe you can accomplish this with incremental update. With incremental update you can add specific errata, packages, or module streams directly to a content view version in a “point release” of that version. The command would look something like:

hammer content-view version incremental-update --content-view-version-id <id> --packages <package1>,<package2>,... --lifecycle-environments <env1>,<env2>,...

Let me know if you have any troubles with incremental update.

Thank you @iballou
I will give it a try. I was just wondering if the same can be accomplished via the foreman UI?

Incremental updating from the UI is limited to applying errata to hosts, so Hammer will be your best bet here.

Thank you @iballou
The solution you provided has worked.

1 Like