Force exclude does not work for individual keys

Created on 2 December 2021, about 3 years ago
Updated 4 January 2024, about 1 year ago

Problem/Motivation

I would like to use config filter to ignore most configuration and then selectively choose what configuration to handle normally using force excludes.

Examples of configuration that I would like to manage normally is the site 403 page while the site name should be ignored. Both are part of the system.site configuration entity.

Steps to reproduce

1. Install Drupal with Config Ignore 2.3
2. Configure config ignore with the following settings:

*
~system_site:page.403

3. Configure the site settings with the `/user/login` path as the 403 page and "Drupal" as the site name
4. Export configuration
5. Configure the site settings with `/foo` as the 403 page and "My Drupal" as the site name
6. See the configuration status
7. I would expect to see that there were changes to the 403 path but not to the site name.

I have not checked whether this problem also exists for 3.x.

Proposed resolution

The logic for managing force excludes does not seem to manage keys. This is also referenced in other comments Add possibility to ignore only certain keys and not the whole coniguration entity. Fixed .

Update the logic to do so.

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

🐛 Bug report
Status

Closed: outdated

Version

2.3

Component

Code

Created by

🇩🇰Denmark kasperg

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

Comments & Activities

Not all content is available!

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

  • 🇨🇭Switzerland bircher 🇨🇿

    This issue is being closed because Config Ignore 2.x is deprecated.

    The new 3,x version has been re-written from the ground up and works in a totally different way, yet it provides the same backwards compatible functionality. All the 2.x tests pass in 3.x and the 3.x codebase is easier to maintain.
    Users of 2.x are strongly encouraged to upgrade to 3.x, as there is a very simple update path.

    So likely this issue is no longer relevant. If you think that this issue still applies please open it again and target the new branch. All issues on the 2.x branch were closed in bulk.

Production build 0.71.5 2024