Problem/Motivation

#2579637: Handle optional configuration in exclude assignment plugin introduced a regression.

When reviewing features differences, optional config shows up whether or not it's valid for import. For example, if language configuration is present in config/optional and the language module is not enabled, the language configuration will show up with a checkbox for importing when reviewing differences. (In practice, no optional configuration seems to import on this screen, regardless of whether or not it's valid.)

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

nedjo created an issue. See original summary.

kerasai’s picture

kerasai commented

I'm finding that import is attempted for optional config, even if its dependencies aren't met.

I'm not sure if this is something that should be addressed by Features itself, or expected to be handled by the underlying core config management system.

Adding a small bit of code to \Drupal\features\FeaturesManager::detectMissing to verify dependencies are available may be one option. My only concern is that the it's probably not trivial to determine which dependencies are met as optional config starts being imported.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Active » Closed (duplicate)

The issue would need to be addressed in Config Update, where this issue is open: #2852638: RevertInterface::revert() and ::import() do not handle config dependencies.