-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
insights-content
Feature Overview
We would like to set the groundwork to enable partner repositories, even though we are not sure how they may be needed in the future. It has been discussed many times in the past, and discussions with copr could make it a reality.
A repository, created by a select organization, would be able to mark their repository as a 'partner repository'. This would allow it to be seen and used by all users (this would need to be communicated properly). This partner repository could pull content from an external place, or have rpms upload to it.
Background and Strategic Fit
There has been many discussions about partner repositories over the years either defined by us, or maintained by a third party. More recently copr support has been discussed
Goals
Allow specific orgs owned by partners to create repositories that are exposed (read only) to all users within console dot.
Requirements
| requirement | Notes | Is Mvp? |
| A specific set of orgs can create a repository and mark it as public. | Y | |
| A partner repository can either sync from an external source or have rpms uploaded to it, creating a snapshot. | Y | |
| A partner repository snapshot can be marked as 'published'. | Y | |
| Partner repositories with at least one public snapshot are visible to all users, consumable, and can be added to a template. | Y | |
| Partner repositories are clearly marked as 'partner' and with information about who provides them. | Y |
Non-Functional Requirements
Since this is just laying the groundwork and not actually enabling any specific partners, we are
Use Cases (User Experience & Workflow)
For the partner:
- The partner would login and navigate to repositories
- the partner would create a repository and mark it as 'public' (or shared, or whatever)
- The partner would either snapshot an external repo, or upload some repositories, creating a snapshot
- The partner would test the resulting repository snapshot
- The partner would mark the snapshot as 'published'
For the user:
- The user would login and navigate to repositories
- The user would have some filter to only see 'partner repositories'
- The user would see shared partner repositories
- The user could navigate to content templates and add these repositories to their template
- The user could navigate to image builder and add these repositories to their image blueprint
Customer Considerations
Customers may want to hide these so they don't show up?
Is there a security concern for red hat or customers?
Customer Information/Supportability
< What information do we need to collect to inform further decision making - SRE metrics. Enumerate aspects of customer feedback, information, metrics and other information that is needed for the Data Driven development, including expectations on user observability. >
Documentation Considerations
- We would need to document this new repository type