Merge ~lutostag/layer-snap:use_juju_proxy into ~stub/layer-snap:master
Proposed by
Greg Lutostanski
Status: | Merged |
---|---|
Merged at revision: | 860fa5723c7e82c919b334181f5c0e0d41ff4ad3 |
Proposed branch: | ~lutostag/layer-snap:use_juju_proxy |
Merge into: | ~stub/layer-snap:master |
Diff against target: |
43 lines (+16/-4) 1 file modified
reactive/snap.py (+16/-4) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stuart Bishop | Approve | ||
Review via email:
|
Description of the change
Use proxying env vars from juju (with config option to disable).
So we don't have to set the proxy to the same as juju model proxy config for every charm we deploy.
To post a comment you must log in.
Do we actually want the configuration item?
I can't think of any situation where people set http_proxy but do not want it used to access the snap store (as opposed to apt_http_proxy, where that would be very wrong)
Unless we have actual use cases, I'd like the config option removed. We can add it later if needed, but I'd rather not have it polluting the config namespace of all charms using the layer if it isn't needed.
(and now I see this MP, perhaps the separate snap_proxy config item was a bad idea. Maybe we should deprecate that, if we can one day remove it without breaking actual deployments.)