Plugins » Katello

As discussed here https://community.theforeman.org/t/question-can-we-automatically-trigger-the-creation-of-a-new-content-view-version-when-a-repo-changes/27960/8 it would be very beneficial to support the following workflow:
- a product contains x number of repositories, each updated either manually or via a sync plan
- those repositories are used in content views
- whenever one of those repositories gets updated during a sync (added or removed content), it should trigger a "publish new version" of all content views containing this repository

As this is only happening to regular CVs and happens only to the Library, no host should be immediately affected (unless hosts are assigned directly to the Library). The same is true for smart proxies, which also should not replicate the Library.

The result would be, that the admin sees new versions published of those content views, were at least one repository was changed during the previous sync. It would also trigger (with the already existing option) an CCV publish if configured. Depending on the individual requirements, the admin can then decide to promote those changes.

If this proposed option would be selectable for each repository as "false", "true" or "unset" (and the default value for "unset" should be settable in the system config), individual repositories could be included/excluded from this behavior. Hence if the default setting would be "false", the admin updating to a Katello release with this new function wouldn't see any change. If the default gets changed to "true", all repos would start publishing associated CVs.

Combined with an optional email notification, this would provide a more streamlined workflow for admins with many repos/CVs and makes sure that critical updates are readily applied to the content hosts.

As a side note, the hammer cli command could be used to cleanup older and no longer referenced CVs, so the danger of having to deal with 100+ historical CV versions can be mitigated.