Project

General

Profile

Feature #33456

Tracker #33447: Alternate Content Sources Support Tracker (MVP)

As a user, I can CRUD RHUI ACSs via the API and hammer

Added by Ian Ballou over 1 year ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Lucy Fu
Category:
Repositories
Target version:
Katello Backlog
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/Katello/katello/pull/10310
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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 over 1 year 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 over 1 year ago

  • Target version set to Katello 4.3.0

#3 Updated by Ian Ballou over 1 year ago

  • Target version changed from Katello 4.3.0 to Katello Backlog

#4 Updated by Samir Jha over 1 year ago

  • Triaged changed from No to Yes

#5 Updated by Ian Ballou 2 months ago

  • Assignee set to Lucy Fu
  • Status changed from New to Resolved
  • Category set to Repositories
  • 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

Also available in: Atom PDF