Bug #34897: Assign HTTP Proxies to ACSs per smart proxy rather than per ACS - Katello - Foreman

Bug #34897

Assign HTTP Proxies to ACSs per smart proxy rather than per ACS

Added by Ian Ballou 10 months ago. Updated 5 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Ian Ballou

Category:

Foreman Proxy Content

Target version:

Katello 4.7.0

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

https://github.com/Katello/katello/pull/10300

Fixed in Releases:

Katello 4.7.0

Found in Releases:

Red Hat JIRA:

Description

We determined that ACS children will likely need different HTTP Proxies depending on what smart proxy they're assigned to. So, we should move the HTTP Proxy selection to the smart proxy from the ACS. It likely doesn't make sense for ACSs on a single smart proxy to be talking to upstream servers via different HTTP Proxies.

Related issues

Associated revisions

Revision e95e87ef (diff)
Added by Ian Ballou 5 months ago

Fixes #34897 - select ACS HTTP proxies per smart proxy (#10300)

Fixes #34897 - ACS HTTP proxies per smart proxy

Refs #34897 - add use_http_proxies to UI and correct verify_ssl

History

#1 Updated by Ian Ballou 10 months ago

Triaged changed from No to Yes

#2 Updated by Ian Ballou 10 months ago

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

#3 Updated by Ian Ballou 9 months ago

Simplified ACSs will likely inherit HTTP Proxy config from their respective repositories. I'm thinking that, on the smart proxy page, there could be an option to select:
1) Inherit from repository
2) Use global default
3) Use specific HTTP proxy

This should be further discussed and designed out, however.