After discussions with the snapd team, it was decided that Juju wouldn't write a file to disk like it did with the http proxies, but instead call snap directly to set the values.
`sudo snap get core proxy` will give you the proxies used for snapd.
```
$ sudo snap get core proxy
Key Value
proxy.http
proxy.https
proxy.store
```
If you call with just a single value, `sudo snap get core proxy.http` you will get the value back.
Juju doesn't expose the snap proxy variables to the charm because they shouldn't need to know.
I don't know why the snapd team hasn't closed bug 1533899.
Older versions of Juju don't write the values out. I'd recommend that the snap layer changes to using
sudo snap set core proxy.http=foo proxy.https=bar
to set the proxy values, rather than writing a file out.
After discussions with the snapd team, it was decided that Juju wouldn't write a file to disk like it did with the http proxies, but instead call snap directly to set the values.
`sudo snap get core proxy` will give you the proxies used for snapd.
```
$ sudo snap get core proxy
Key Value
proxy.http
proxy.https
proxy.store
```
If you call with just a single value, `sudo snap get core proxy.http` you will get the value back.
Juju doesn't expose the snap proxy variables to the charm because they shouldn't need to know.
I don't know why the snapd team hasn't closed bug 1533899.
Older versions of Juju don't write the values out. I'd recommend that the snap layer changes to using
sudo snap set core proxy.http=foo proxy.https=bar
to set the proxy values, rather than writing a file out.