Config ignore settings should have lower priority or be completely ignored during site:install

Created on 14 September 2022, over 2 years ago
Updated 4 January 2024, about 1 year ago

Problem/Motivation

When configuration exported is using drush config:export and afterwards using that configuration to install fresh profile with drush site:install --existing-config it imports config_ignore configuration, thus resulting in missing configuration after site installation.

Indicating message during site:install:

[notice] Missing required data for configuration: system.maintenance

Steps to reproduce

  1. Perform fresh installation of standard profile.
  2. Install Config Ignore
  3. Configure Config Ignore to ignore 'system.maintenance'
  4. Export configuration using drush config:export
  5. Perform fresh installation of standard profile using drush site:install --existing-config
  6. Console will output these errors after modules and themes are installed and enabled

Proposed resolution

Config Ignore configuration should be imported as final stage of installation process, rather than as any normal module, to prevent missing configuration messages as Drupal supports installing from existing configuration from the core.

Feature request
Status

Closed: outdated

Version

2.0

Component

Code

Created by

🇱🇹Lithuania irmantasp

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.

  • 🇮🇳India prashant.c Dharamshala

    But how you were able to install standard profile with existing configs, it only works with minimal as far as I tried
    https://www.drupal.org/node/2897299 .

    Therefore for me in steps to reproduce it is failing on Step 5.

    Thank you.

  • Status changed to Closed: outdated about 1 year ago
  • 🇨🇭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