Contrib.social

Config ignore not ignoring config keys when using specific keys

Open on Drupal.org →
Created on 5 May 2023, about 1 year ago
Updated 21 October 2023, 8 months ago

Problem/Motivation

Key/value combinations that point to a 'specific' value of a key in a config file are being imported even if they exist in config ignore.

Steps to reproduce

Install reroute_email module
Configure reroute email and add an address to the 'reroute address' field.
Add reroute_email.settings:address to config ignore.

Change the value of 'reroute address' on the site and re-import configuration. It will detect the file, and will import it, overwriting the 'reroute address' in the database with the one in the reroute_email.settings.yml file.

I have been able to validate this with other modules as well, so it's not reroute email specific. Any entry in config ignore that uses a specific key (e.g. config.name:key) gets imported. (Another example is the site settings email. If you enter system.site:mail into config ignore it still overwrites the basic site email address.

🐛 Bug report
Status

Closed: cannot reproduce

Version

3.0

Component

Code

Created by

🇺🇸United States jfurnas

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

Comments & Activities

  • Issue created by @jfurnas
  • Comment about 1 year ago →
    🇺🇸United States jfurnas
  • Comment about 1 year ago →
    🇺🇸United States jfurnas

    Can I get a bump on this please? This has become an extreme burden as we are doing active development and keep getting our emails rerouted numerous times a day because config_ignore is not ignoring the settings and is instead changing them.

  • Status changed to Postponed: needs info about 1 year ago
  • Comment about 1 year ago →
    miiimooo Europe

    @jfurnas I use config_ignore with a similar format `something.settings:setting` and it's working as designed

  • Status changed to Closed: cannot reproduce 8 months ago
  • Comment 8 months ago →
    🇨🇭Switzerland bircher 🇨🇿

    The code has been refactored quite a bit, and I believe that we have automated tests covering this scenario.

    But please open the issue again or create a new one and attach a test case so that we can find out what is going on.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024