Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-28495

Rolling Content Views

XMLWordPrintable

    • Rolling Content Views
    • In Progress
    • Phoenix - Content
    • False
    • sat-artemis
    • Feature
    • Hide
      .Rolling content views

      You can now create rolling content views in Satellite to provide hosts with a continuous stream of the latest synchronized content from a defined subset of repositories.

      Unlike standard or composite content views, rolling content views are automatically updated whenever their repositories are synchronized, so there is no need to publish or promote them.

      Administrators can create rolling content views in the Satellite web UI or CLI and then assign them to activation keys to make the content available to registered hosts.
      Show
      .Rolling content views You can now create rolling content views in Satellite to provide hosts with a continuous stream of the latest synchronized content from a defined subset of repositories. Unlike standard or composite content views, rolling content views are automatically updated whenever their repositories are synchronized, so there is no need to publish or promote them. Administrators can create rolling content views in the Satellite web UI or CLI and then assign them to activation keys to make the content available to registered hosts.
    • Done

      See https://community.theforeman.org/t/transparent-content-view-for-limiting-repository-access-in-katello/39389/

       

      Goal:

       

      • Introduce a new type of "simplified" content view, for users who only want to limit access to repositories, but do not need snapshots, publish/promote, or filtering.
      • This new CV type will behave like Default Organization View does, but it will only expose a subset of Library repositories.
        • No publishing
        • No promotions
        • No CV filters
        • Content is updated immediately on sync
        • Can reuse Content View details UI page, but hide most tabs
        •  

      Acceptance Criteria:

      • The code was developed by community members and is now in review. The documentation is also in review. We will need to add QE automation for the feature.

              Unassigned Unassigned
              rhn-engineering-jlenz Jeremy Lenz
              Brian Angelica Brian Angelica
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: