Uploaded image for project: 'Insights Experiences'
  1. Insights Experiences
  2. HMS-5827

api - Add shared EPEL repositories for list/fetch

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Content
    • insights-content
    • Repositories 0, Content 1, Content 2
    • 5

      Goal: 

      • Rather than having the user create a custom EPEL repository, we should have a shared repository (similar to red hat repos). This could be seen and used by any user without having to create a custom repository for EPEL.

      Acceptance Criteria:

      • Community repositories are returned in list and fetch calls for any org
      • List can filter by community repositories only, e.g. 
        /repositories/?origin=community
      • Community repositories have their own org and pulp domain
      • Community repositories should be introspected and snapshotted as part of process-repos
      • Add check in validation API to prevent creation of custom EPEL repos in the UI. Creation through API will be addressed separately.
      • User should not be able to create, delete, or edit community repositories
      • User can list packages and snapshots for community repositories, or anything a red hat repo allows

              rverdile@redhat.com Ryan Verdile
              rverdile@redhat.com Ryan Verdile
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: