Allow for disabling built-in rate limiting

Bug #1910977 reported by Tom Haddon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-k8s-discourse
High
Unassigned

Bug Description

As of Discourse 2.6.0 anonymous rate limiting was made much more aggressive than previously.

We need a way to be able to disable that rate limiting in the charm.

Related branches

Revision history for this message
Jay Kuri (jk0ne) wrote :

I believe the best solution here is to change how Discourse is obtaining its GlobalSettings to work from the environment. This is how the official Discourse docker image handles configuration and would allow the k8s charm to more closely follow the upstream configuration documentation.

We will need to investigate how they accomplish this in the official image.

Tom Haddon (mthaddon)
Changed in charm-k8s-discourse:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Jay Kuri (jk0ne) wrote :

Fixed in release f809f08bbf133cd8536e7a2bd1dd4bf3ce84f29c

Changed in charm-k8s-discourse:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers