Project

General

Profile

Actions

Refactor #31796

closed

Container Gateway should handle using default proxy certs differently

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

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Container
Target version:
Branch:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

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 open1 closed)

Related to Katello - Bug #31982: Smart Proxy Container Gateway calls Proxy::Settings.initialize_global_settingsClosedEwoud Kohl van WijngaardenActions
Actions

Also available in: Atom PDF