Actions
Feature #33456
closedTracker #33447: Alternate Content Sources Support Tracker (MVP)
As a user, I can CRUD RHUI ACSs via the API and hammer
Description
This feature will require some information about how RHUI is going to provide config information to Katello.
Current proposed idea:
1) User gets a JSON config file from rhui-manager
2) The user creates an ACS in Katello with a name, description, smart proxies, and pasted/uploaded JSON config
-> If the JSON config can have one cert/key for all the chosen repos, no need to enter a product
-> If there are separate certs per product, the product will need to be specified here
Updated by Ian Ballou about 3 years ago
- Subject changed from As a user, I can CRUD RHUI ACSs to As a user, I can CRUD RHUI ACSs via the API and hammer
Updated by Ian Ballou about 3 years ago
- Target version changed from Katello 4.3.0 to Katello Backlog
Updated by Ian Ballou over 1 year ago
- Category set to Repositories
- Status changed from New to Resolved
- Assignee set to Lucy Fu
- Pull request https://github.com/Katello/katello/pull/10310 added
RHUI ACSs (for now) through the UI/API will require all information to be added manually, like custom. In the future, it will be make simpler: https://issues.redhat.com/browse/RHUI-134
Actions