Block writing of enforced config

Created on 12 August 2020, over 4 years ago

Updated 18 September 2024, 7 months ago

We currently advertise 3 levels of enforcement:

The last of these, "Read-only, no updates", has not yet been implemented.

With Config Enforce Devel, flag a given config form as enforced, and set the level of enforcement to "Read-only, no updates".
Disable Config Enforce Devel.
Visit the "Edit Config" page provided by the Devel module.
Edit and save the config that was flagged in Step 1.
Observe that the config can be saved.

Implement event listeners, or an alternative storage service that will block writes to config.

TBD

None.

None.

TBD

✨ Feature request

Status

Active

Version

1.0

Component

Code

Created by

🇨🇦Canada ergonlogic Montréal, Québec 🇨🇦

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 7 months ago →
🇨🇦Canada ergonlogic Montréal, Québec 🇨🇦
Configuration Read-only mode → now supports a hook (hook_config_readonly_whitelist_patterns()) that would allow us to specify whatever config is set to Level 1 & 2 enforcement. This'd have the effect of locking down Level 3 config (this feature request), as well as any unenforced config (which seems prudent anyway).

Alternatively, there's already a feature request for #3085001: Config blacklist to only block some configuration while in read only mode →

Production build 0.71.5 2024