Feature #38048
closed
Add rolling content views
Description
Motivation:
With the switch to simple content access, it is no longer possible to limit the repositories from the "Default Organization View" using subscriptions.
Instead, any host consuming the "Default Organization View" will have access to all the repositories in Katello.
Host side enable/disable as the only point of restriction.
This is especially critical where license agreements do not allow making repos available on unlimited numbers of hosts, essentially rendering the "Default Organization View" unusable in such business contexts.
The Idea:
Add a new type of simplified content view ("Rolling") that allows passing latest synced content directly to consuming hosts (like the default organization view), but also allows this to be limited to arbitrary user chosen repo sets.
Community RFC thread: https://community.theforeman.org/t/transparent-content-view-for-limiting-repository-access-in-katello/39389
Updated by The Foreman Bot 4 months ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/11240 added
Updated by The Foreman Bot 4 months ago
- Pull request https://github.com/Katello/hammer-cli-katello/pull/974 added
Updated by
Updated by Quirin Pamp 4 months ago
- Related to Bug #38076: The content view APIs will pass repository_ids to the code both as a list of int or a list of strings added
Updated by Quirin Pamp 22 days ago
- Related to Bug #38284: Syncing rolling content views to smart proxies does not update proxy content counts added
Updated by Quirin Pamp 22 days ago
- Related to Bug #38285: Disallow pushing containers to rolling content views added
Updated by Manisha Singhal 22 days ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|a300f9707f3e4c62eaa3e8856e6fe3989f2f9f6d.