Handle the public IP and SSL certificate set by the haproxy charm
Bug #1442533 reported by
Free Ekanayaka
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Charm |
Fix Released
|
Medium
|
Free Ekanayaka |
Bug Description
For the case where the user does not specify an SSL certificate and root-url and we rely on the defaults of the haproxy charm, we should look at the relevant information that the haproxy charm sends us (IP and SSL certificate) and use it as default values for our own ssl-cert and root-url config keys.
See also Bug #1442529.
Related branches
lp:~free.ekanayaka/landscape-charm/handle-haproxy-ip-and-cert
- 🤖 Landscape Builder: Approve (test results)
- Chris Glass (community): Approve
- Björn Tillenius (community): Approve
-
Diff: 519 lines (+223/-27)10 files modifiedhooks/lib/callbacks/filesystem.py (+35/-0)
hooks/lib/callbacks/tests/test_filesystem.py (+44/-1)
hooks/lib/relations/haproxy.py (+23/-13)
hooks/lib/relations/tests/test_haproxy.py (+15/-1)
hooks/lib/services.py (+8/-3)
hooks/lib/tests/sample.py (+8/-0)
hooks/lib/tests/test_services.py (+52/-2)
hooks/website-relation-changed (+9/-0)
tests/01-begin.py (+23/-7)
tests/helpers.py (+6/-0)
tags: | removed: kanban |
description: | updated |
Changed in landscape-charm: | |
status: | In Progress → Fix Committed |
Changed in landscape-charm: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Just a comment in passing: We need to make sure what happens here is very easy to figure out from looking at the logs, since I suspect it would be a nightmare to debug otherwise (log profusely).