After update: config split not working anymore [#3166114]

Hi,

I just ran composer update which leads to an update of config filter from version 1.5.0 to 2.0.0. I believe it is added as a dependency of config split module which I use to define which modules and configs should be active in development environment.

After drush updb (no updates were needed) I called drush cex. I realized that now the configs which were exported to a specific subfolder (for the development environment configs) before now were exported to the default sync folder. During deployment to stage which does not use the development configs I realized that these development environment configs are now imported.

There were some more updates such as Drupal core from 8.9.2 to 8.9.3 and some libraries shipped by Drupal core but I believe this new behavior for configs which were split before is caused by the update of this module. Does anyone else have this issue?

Best,
Tobias

Comments

Comment #1

19 August 2020 at 14:53

tobiberlin created an issue. See original summary.

Comment #2

tobiberlin

German

Berlin, Germany

commented 19 August 2020 at 15:01

I downgraded back to 1.5 version - no changes. So it might be an issue with some of the other updates

Comment #3

19 August 2020 at 15:40

bircher committed cbde166 on 8.x-2.x

Issue #3166114: add conflict with drush 9

Comment #4

bircher

🇨🇿

commented 19 August 2020 at 15:44

Which version of drush are you using?
I added a incompatibility with drush 9 to config_filter 2.x because drush 9 does not use the new core API

Comment #5

tobiberlin

German

Berlin, Germany

commented 19 August 2020 at 16:01

Thank you - this was the point... after updating to Drush 10 (I used drush 9) everything works again as expected.

Comment #6

bircher

🇨🇿

commented 24 August 2020 at 16:14

Status:

Active

» Fixed

@mixologic from the Drupal association was kind enough to unpublish the 2.0 release node so that people using composer should get the correct version depending on which version of drush they use.

Thanks for finding this and thanks for helping with the infra.

Comment #7

weseze commented 27 August 2020 at 15:40

Seems like to 2.0 is still available somehow, perhaps in caching somewhere?
I setup a new project today, just a few hours ago, and got the 2.0 version...

Is this possible? Should this problem go away once all caching layers (d.o., packagist, ...) are rebuilt? Or does the 2.0 still really exist somewhere?