Temporary Kill Switch?

Created on 23 August 2024, 8 months ago

Updated 3 September 2024, 7 months ago

Love this module

Problem/Motivation

I'm looking for a way to temporarily suspend readonly programmatically.

I have a situation where I want to allow programmatic updates to configuration without whitelisting configuration to be writable.

I'm thinking about a service method that I can patch into a module to allow the module to update some configuration.

In CiviCRM there are custom fields for that system, that is separate from Drupal. Drupal configuration management does not apply there.

When the Drupal module Webform CiviCRM is installed, and an admin updates a CiviCRM field, there is a CiviCRM hook that runs, and Webform CiviCRM module scans Webform configuration if the Civi custom field is used, and updates Webform configurations todo with that custom field.

I want to allow this to happen, but still keep Webform configuration locked down for when people edit the Webform through normal means.

Is this currently possible, or ideas on how could this be made possible?

💬 Support request

Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States markusa

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @markusa
Comment 7 months ago →
🇺🇸United States trackleft2 Tucson, AZ 🇺🇸
Check the front page of the https://www.drupal.org/project/config_readonly → project for suggestions on how to strategically enable or disable config_readonly
Comment 7 months ago →
🇺🇸United States markusa
I've read the front page before. None of those methods work for my use case, its not nimble or specific enough.

I've patched this module and webform_civicrm to use drupal_static() to make a conditional decision on whether to allow config_readonly programmatic config updates for a very specific use case, for a particular .

This may evolve into a patch that could be used for general usage.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024