Graylog web_endpoint_uri is not configurable via charm
Bug #1834352 reported by
Jeremy Lounder
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Graylog Charm |
Fix Released
|
High
|
Jeremy Lounder |
Bug Description
Graylog has several settings used to configure access for the API and Website. The primary three are web_listen_uri, rest_transport_uri, and web_endpoint_uri.
The charm is currently missing the ability to configure web_endpoint_uri - this makes it impossible to access the Graylog website from an external IP address when using a reverse proxy - such has haproxy. The proxy forwards web traffic to the web_listen_uri, but Graylog returns the rest_transport_uri as the default value for web_endpoint_uri - which is typically configured as an internal IP address used for cluster communications.
Related branches
~graylog-charmers/charm-graylog:graylog-webinterface
Merged
into
~graylog-charmers/charm-graylog:master
at
revision cd52b80f45273f8627bf18d86b38c2ea688808ee
- Chris Sanders (community): Approve
- Stuart Bishop (community): Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 82 lines (+45/-2)2 files modifiedconfig.yaml (+14/-1)
reactive/graylog.py (+31/-1)
Changed in graylog-charm: | |
importance: | Undecided → High |
assignee: | nobody → Jeremy Lounder (jldev) |
status: | New → Incomplete |
status: | Incomplete → In Progress |
Changed in graylog-charm: | |
status: | In Progress → Fix Released |
To post a comment you must log in.