Actions
Refactor #31796
closed
Container Gateway should handle using default proxy certs differently
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
Updated by James Jeffers about 4 years ago
- Target version set to Katello 4.1.0
- Triaged changed from No to Yes
Updated by Ewoud Kohl van Wijngaarden almost 4 years ago
- Related to Bug #31982: Smart Proxy Container Gateway calls Proxy::Settings.initialize_global_settings added
Updated by Ewoud Kohl van Wijngaarden almost 4 years ago
- Status changed from New to Duplicate
Looks like I didn't see this and opened #31982 instead for which the fix was merged.
Actions