if you check the crowdsec settings with https://www.drupal.org/project/config_inspector → in the command line it lists three schema errors:
$> ddev drush config:inspect --filter-keys=crowdsec.settings --detail
➜ 🤖 Analyzing…
Legend for Data:
✅❓ → Correct primitive type, detailed validation impossible.
✅✅ → Correct primitive type, passed all validation constraints.
-------------- ------------------------------------------ ------------- ------
Key Status Validatable Data
-------------- ------------------------------------------ ------------- ------
crowdsec.set missing schema
tings:log_le
vel
crowdsec.set variable type is integer but applied
tings:api_ti schema class is
meout Drupal\Core\TypedData\Plugin\
DataType\StringData
crowdsec.set variable type is integer but applied
tings:whispe schema class is
r.enable Drupal\Core\TypedData\Plugin\
DataType\BooleanData
-------------- ------------------------------------------ ------------- ------
Failed to run drush config:inspect --filter-keys=crowdsec.settings --detail: exit status 1Aside the errors the schema is at 17% validatability.
drush config:inspect --filter-keys=crowdsec.settings --detailadmin/reports/config-inspectorActive
1.1
Code
not sure if those changes are reasonable and enough in scope and or valid but at least the errors are fixed and the config inspector lists the schema as 100% validatable now.
This is great, thank you so much @rkoller for contributing this. I left a couple of comments, not sure how one of them can and should be addressed, though.