Skip to content

no_proxy is not respected during index searches #5497

@minsis

Description

@minsis

SUMMARY

This isn't exactly a bug (kinda?) but maybe a solution to consider in how implement this.

Basically no_proxy is ignored during pack index searches.

if proxy_config:
https_proxy = proxy_config.get("https_proxy", None)
http_proxy = proxy_config.get("http_proxy", None)
ca_bundle_path = proxy_config.get("proxy_ca_bundle_path", None)
if https_proxy:
proxies_dict["https"] = https_proxy
verify = ca_bundle_path or True
if http_proxy:
proxies_dict["http"] = http_proxy

This makes obvious sense because if you're behind a proxy you want to be able to search the st2 Exchange Index. The issue comes in when you have a local index like I do. The local index is hosted on our controller node and the proxy doesn't have access to this URL due to FW rules. Proxy isn't local to the datacenter either. So because no_proxy isn't respected in an index search my custom index is unreachable.

To further complicate things, I also search the Exchange Index, meaning I have specified both internet based and a local based index. The internet based obviously needs to go though the proxy, but the local based one can't.

The only real way to by pass this at this point is to specify our internal git URL directly and the pack will install since its not searching the index.

Not sure if anyone else has this issue, it might be extremely specific to me with our locked down environment.

STACKSTORM VERSION

Paste the output of st2 --version:
st2 3.6.0, on Python 3.6.8

OS, environment, install method

3 node HA cluster: 2 nodes, 1 controller all three behind a load balancer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions