haproxy should wait to write out a front end and backend until they are configured by relating service OR allow configuration of the default frontend/backend
Bug #1770890 reported by
james beedy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-haproxy |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
The haproxy charm writes out a default front end and backend that bind to port 80.
This is a blocker for charms that want to specify custom service relations to haproxy that bind to port 80.
Can we not write out a frontend/backend just for the heck of it, and wait until relations specify what they want to bind to?
OR
Allow configuration of the default frontend/backend?
| summary: |
haproxy should wait to write out a front end and backend until they are - configured by relating service + configured by relating service OR allow configuration of the default + haproxy_service |
| summary: |
haproxy should wait to write out a front end and backend until they are configured by relating service OR allow configuration of the default - haproxy_service + frontend/backend |
| description: | updated |
| description: | updated |
| Changed in charm-haproxy: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Martin Eckerwall (martymartmart) wrote | #1 |
To post a comment you must log in.
Setting the config option service to an empty string helps avoid this ("Can we not write out a frontend/backend just for the heck of it, and wait until relations specify what they want to bind to?")
juju deploy haproxy --config services=""