Merge ~mitchburton/landscape-charm:2059194-respect-juju-proxy-settings into landscape-charm:main
Status: | Merged |
---|---|
Approved by: | Mitch Burton |
Approved revision: | fbbc33e330a6148c065f43570d89d4ed842d34d6 |
Merged at revision: | dfc4418011daa43a9ce051259a2dcf4bbd0d19e1 |
Proposed branch: | ~mitchburton/landscape-charm:2059194-respect-juju-proxy-settings |
Merge into: | landscape-charm:main |
Diff against target: |
148 lines (+57/-7) 2 files modified
src/charm.py (+37/-4) tests/test_charm.py (+20/-3) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ardavan Behnia | Approve | ||
Landscape | Pending | ||
Review via email: mp+464054@code.launchpad.net |
Commit message
use JUJU_*_PROXY env vars on bootstrap
Description of the change
This change uses the juju proxy-related model configs to populate Landscape's proxy configuration on initial setup. After initial setup, the proper way to change them is through the Landscape UI.
Don't use `make build` to test this, as it'll be too late to update the model config (there's no "model-
1. make clean
2. charmcraft pack
3. juju add-model landscape-charm-dev
4. juju model-config juju-http-proxy=http://<proxy_
5. juju deploy ./bundle.yaml
6. log into Landscape via haproxy's IP address and click on "settings" for the account. Ensure that the proxy settings appear there.
There's currently an in-review MR for landscape-server that makes the appserver process actually respect these settings.
Manually checked with (squid) and without proxy, left a small question inline.