Refactor #31796: Container Gateway should handle using default proxy certs differently - Katello - Foreman

Actions

Copy link

Refactor #31796

closed

Container Gateway should handle using default proxy certs differently

Added by Ian Ballou over 4 years ago. Updated over 4 years ago.

Status:

Duplicate

Priority:

Normal

Assignee:

Category:

Container

Target version:

Katello 4.1.0

Branch:

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Currently we use `initialize_global_settings` in the Container Gateway, which might cause initialization issues. It would be worth investigating this and considering changing the strategy. The proxy's default SETTINGS are nil during the default initialization code, so the default cert settings would have to be loaded dynamically during runtime. SETTINGS is properly set during the actual runtime of the Container Gateway.

A proposed alternate solution can be found here in the discussion here: https://github.com/Katello/smart_proxy_container_gateway/pull/10

Related issues 1 (0 open — 1 closed)