livepatch-charmers team mailing list archive

[Barry Price <barry.price@xxxxxxxxxxxxx>]

Barry Price has proposed merging ~barryprice/canonical-livepatch-charm/+git/canonical-livepatch-charm:master into canonical-livepatch-charm:master.

Commit message:
Documentation update

Requested reviews:
  Livepatch charm developers (livepatch-charmers)

For more details, see:
https://code.launchpad.net/~barryprice/canonical-livepatch-charm/+git/canonical-livepatch-charm/+merge/348746
-- 
Your team Livepatch charm developers is requested to review the proposed merge of ~barryprice/canonical-livepatch-charm/+git/canonical-livepatch-charm:master into canonical-livepatch-charm:master.

diff --git a/README.md b/README.md
index 6c8562e..a5c94e4 100644
--- a/README.md
+++ b/README.md
@@ -28,10 +28,14 @@ Or via juju config (Juju 2.x)
 
 The livepatch_key setting must be configured in order for the software to function correctly - see above.
 
-By default, the livepatch software will attempt to retrieve its patch data directly over the network. If you'd like to use an HTTPS web proxy for this traffic instead, you can set the livepatch_proxy value to the address of your proxy server.
+By default, the livepatch software will attempt to retrieve its patch data directly over the network. If you'd like to use a proxy for this traffic instead, you can set the livepatch_proxy value to the address of your proxy server.
 
 Likewise, if you need to use a proxy server to access the Snap Store, snap_proxy can also be set to the address of your proxy server.
 
+Alternatively, if you've configured a proxy for all applications in your environment via juju model-config, the charm will detect this and automatically do the right thing. It'll use http-proxy or https-proxy if either are set, with the latter being preferred.
+
+If two different proxies are set via model config and charm config, the latter will be preferred.
+
 # Contact Information
 
 This charm is maintained here, by the livepatch-charmers team: