Add Support for no_proxy environment variable

[chris2215]

Describe the enhancement
It would be helpful if the "Sync Destination" feature would respect the no_proxy environment variable. We have a Databricks environment that is secured within a VNET. All requests going to Databricks should not use the proxy. As a current workaround, we set "export https_proxy=", but this means no requests go through the proxy anymore. For instance, Databricks Connect can no longer check its version, resulting in the error: "Command failed: /usr/local/bin/python3.11 -m pip index versions databricks-connect...".

Screenshots

With "export https_proxy=proxy-server" and "export no_proxy=adb-workspace-id.0.azuredatabricks.net"

Sync Destination ignores no_proxy and uses the proxy:

wget is functional:

With "export https_proxy=" and "export no_proxy=adb-workspace-id.0.azuredatabricks.net"

With "export https_proxy=proxy-server" and "export no_proxy="

System information:

Version: 1.77.0 (system setup)
Commit: 7f329fe6c66b0f86ae1574c2911b681ad5a45d63
Date: 2023-03-29T10:02:16.981Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: No

Databricks Extension Version: 1.1.0

We develop using VS Code and with the Databick Extension on a Debian Remote Server

[fjakobs]

Thanks for the report. It's a bit tricky because The VS Code itself, the extension host where the extension is running and the CLIs we are calling all need to respect the proxy variables. In the past, it has been proven difficult to properly forward the proxy values to all these components.

We'll try to prioritize if but I can't make any promises right now.