Add support for proxies

[emalzer]

Hi!

I started testing and using restsh and face the challenge to use HTTPs proxies with authentication to access F5s. I was already able to work my way around with environment variables to use a proxy and pass or ignore the proxy certificate, but inserting or adding user:pass credentials is more tricky via environment vars. I could only think about a netrc file, but would like to avoid this.

Can you add support for a proxy configuration to be able to set:
proxy_host:port
proxy_cacert and / or proxy_insecure
proxy_user
proxy_pass

Where as user and pass are different from the RESTSH_USER / RESTSH_PASS.

I think if a proxy_host is set in the host configuration file then a prompt for proxy_user / proxy_pass would be fine before prompting for the host user / pass credentials and keeping the creds for the session. If all could be set via environment vars would make it then perfect for CICD!

I'm happy to assist or test if needed.

Greetings from Austria!
Erich

[JuergenMang]

I personally prefer to use direct connection for a simplified setup, but using a proxy with authentication is also viable.

Let me dig into the options curl provides.

[JuergenMang]

There is now a completely untested "proxy" branch that adds some additional configuration variables:

RESTSH_CURL_PROXY_INSECURE="0"
RESTSH_CURL_PROXY_AUTH="basic"
RESTSH_CURL_PROXY_USER="<user>"
RESTSH_CURL_PROXY_PASS="<password>"

The proxy can be set with the standard environment variables http_proxy , https_proxy and no_proxy environment variables. I do not think we need a special handling in Restsh for this.

Testing of your side is highly appreciated.

[emalzer]

I tested it in one of my environments and it works fine! Will do some more testing through out the next days with different environments.

[emalzer]

hey!
my tests are working fine - looks very good to me!

[JuergenMang]

Perfect! I will merge it into master as soon I have time to test it on my side too.