If config/sync dir has a piece of config but profile config does not, it fails to export into the profile.

Created on 30 July 2020, over 4 years ago
Updated 20 May 2024, 8 months ago

Problem/Motivation

Working with config_profile we've noticed that sometimes certain pieces of config don't get exported when they already exist in the "regular" config/sync directory. It's not clear yet under what conditions this happens, but the workaround we've found is to manually (re)move the main config/sync folder, run a `drush cex`, and config_profile will capture all the active config.

Steps to reproduce

I believe there are 2 possible scenarios here:

1. Config that is unchanged in active (but somehow not yet in the profile's config) gets ignored, because it doesn't look like it needs exporting
2. Config that's in active but changed relative to config/sync gets ignored by config_profile, only updating in the config/sync tree

Proposed resolution

No good suggestion at the moment. Ideally I think config_profile (or config_filter?) would be able to distinguish active config differences against its own copy of the exported config, rather than what's in config/sync. Worst case, I suppose the module could (temporarily) remove the config/sync directory and then put it back, but this seems convoluted.

Remaining tasks

* Understand the conditions for reproducing this
* Identify the root cause of the bug: is this a core issue? config_filter? or can we fix it in config_profile?

🐛 Bug report
Status

Postponed: needs info

Version

2.0

Component

Code

Created by

🇨🇦Canada spiderman Halifax, NS

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.

Production build 0.71.5 2024