Feature #33456
Tracker #33447: Alternate Content Sources Support Tracker
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
History
#1
Updated by Ian Ballou 9 months 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
#2
Updated by Jonathon Turel 8 months ago
- Target version set to Katello 4.3.0
#3
Updated by Ian Ballou 8 months ago
- Target version changed from Katello 4.3.0 to Katello Backlog