Feature Overview

Currently when building images, the BaseOS and Appstream repos are used, and the user can select custom repositories to add, but additional red hat repositories cannot be used when building the image.  This feature would allow the user to optionally add additional Red Hat repositories

Background and Strategic Fit

This would enable the Extensions repo in Image builder: https://issues.redhat.com/browse/RHIN-1966

Goals

• Build images with add on repositories such as Code Ready builder and the Extensions repo
• Build images with add on products such as High Availablity

Requirements

Non-Functional Requirements

N/A

Use Cases (User Experience & Workflow)

1. A user would go to Images to build an image
2. Use would create a blueprint
3. User would select RHEL 9
4. User would proceed through the wizard until they get to the "Repositories" step (Formally custom repositories)
5. User could select one or more additional Red Hat repositories in addition to the custom repositories
6. User would continue to the packages screen and add packages from these additional Red Hat repositories
7. User would continue and build the image
8. Built image would contain packages from these custom repositories

Customer Considerations

• Activation Keys - how much do we ensure repositories are enabled after the system boots and is registered.
  • Offer ability to 'clone' activation key and add new repositories
  • Enable repositories in first boot

Customer Information/Supportability

Documentation Considerations

• Documentation updates around the "Custom repositories" wizard step, as well as how to add additional repositories