Charm uses juju-http-proxy config, but not honor juju-no-proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
landscape-client-charm |
Confirmed
|
Undecided
|
Spencer Runde |
Bug Description
When a juju model has juju-http-proxy and juju-https-proxy variables set, and juju-no-proxy is also set, the charm configures the proxies in /etc/landscape/
For instance, if I have:
juju-http-proxy controller http://
juju-https-proxy controller http://
juju-no-proxy model localhost,
And my url is http://
This variable must be parsed and managed by charmers to go hand-in-hand with the use of juju-http(s)-proxy variables.
A workaround is to define http-proxy and https-proxy in the charm config as blank strings with:
juju config landscape-client http-proxy="" https-proxy=""
It seems that if these are "unset" as the default config, then the juju model variables are utilized, but if set to null strings, the juju model configs are ignored and these variables are left unset in the client.conf template.
Changed in landscape-client-charm: | |
status: | New → Confirmed |
Changed in landscape-client-charm: | |
assignee: | nobody → Spencer Runde (spencerrunde) |
This issue is mainly in relation to on-premise landscape-server usage. using the proxy for access to hosted landscape as a service makes sense for most use-cases.