Move autoban_threshold_last, _window_last, and _provider_last out of config, into STATE

Created on 2 May 2024, about 2 months ago

Problem/Motivation

It seems silly that there are config changes in autoban.settings.yml after someone is making changes to a specific rule.

I see stuff like this after making a new rule, or changing an existing rule:

drush config:export --diff

--- a/config/sync/autoban.settings.yml
+++ b/config/sync/autoban.settings.yml
@@ -42,7 +42,7 @@ autoban_dblog_type_exclude: |-
   php
   purge
   system
 autoban_threshold_analyze: '5'
-autoban_threshold_last: '10'
-autoban_window_last: '2 days ago'
+autoban_threshold_last: '8'
+autoban_window_last: '1 week ago'
 autoban_provider_last: ban

Steps to reproduce

Proposed resolution

The three configurations for _last should be moved out of config and into the STATE system in Drupal. Then, as admins navigate the UI and make changes, the site can still remember what these "last" settings were, but they're not exported to code.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ͺπŸ‡¨Ecuador jwilson3

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.69.0 2024