Actions
Refactor #31796
closedContainer 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
Actions