You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wfe/ra: Periodically load rate limit overrides from the database (#8407)
Add a `refreshOverrides` func to the `ratelimits.limitRegistry` struct.
Instead of populating the static `overrides` field once when creating an
instance of the struct, call the new func at startup and then every 30
minutes.
Emit relevant logs and metrics from `limitRegistry`.
Add an `OverridesFromDB` limiter config flag (for RA & WFE) to read
overrides from the DB instead of a file.
Flatten `newLimitRegistry.*()` methods' logic into their sole caller,
`NewTransactionBuilder()`.
Rename `loadDefaults()` & `loadOverrides()`, appending `FromFile` for
clarity/consistency.
test: Add ra-sct-provider dependency on SA.
**Important for deployment:** If the `OverridesFromDB` config flag is
enabled, an RA now depends on the SA in order to load overrides. The RA
must be added as a gRPC client of `sa.StorageAuthorityReadOnly`.
*CPS Compliance Review:* `OverridesFromDB` only controls how we load
rate limit overrides, which has no compliance implications beyond
general API availability (e.g. for revocation). I've checked our CP/CPS
to confirm we make no related stipulations.
Fixes#8382
0 commit comments