Comment 4 for bug 1835050

I agree, as such model-config changes are not something charms have previously reacted to via explicit events and proxy settings are exposed via hook environment variables only.

I think we need to have a design discussion about whether we should special-case some model-config changes to trigger config-changed events or not (and then provide some other mechanism to react to those changes, e.g. a special event and something like a model-get hook tool to fetch a subset of model settings).

There is clearly a need to handle those updates as many charms are polluted with proxy config options. For better or worse it allows charms to set proxy servers on per-use-case basis but most of the charms (in my experience) actually use the same config as the one provided by juju-{http,https,no}-proxy which makes the experience of working with proxies very confusing and error-prone.