Config Ignore + Config Split not working (for me)

Config Ignore's config is ultra simple. I'm wondering if it's something in the preamble of config split

langcode: en
status: false
dependencies: {  }
id: local
label: Local
description: ''
weight: 2
stackable: false
no_patching: false
storage: folder
folder: ../config/local

This seems to be the same issue as 🐛 Splits: Ensure config_ignore works for everyone - set default to functional value Needs review

And how do you expect this to work when you export the config?

And how do you expect this to work when you export the config?

Presumably with the new config_ignore, with a simple config split it should not export or overwrite anything.

Thanks for the other issue link. I'll check this out Monday and see if it's a duplicate.

Hi, could you test your expectations with the split configured to use the collection storage?

If you make the config import subscriber more heavy as suggested in 🐛 Splits: Ensure config_ignore works for everyone - set default to functional value Needs review but also for export and configure the split to use the collection storage then (and use the same config ignore settings on all collection, in particular the ones of splits) then config ignore should "ignore" also the change in your split.

Thanks for your feedback.

@bircher - Acknowledge receipt of message.

This is in my queue - which unfortunately has blown up. I'll see if I can research this next week.

Sorry for taking so long to get back to this.

I've recreated my scenario 4 before and verified it's still failing to behave as expected.

I upgraded to config_ignore 8.x-3.x dev (hash 96094ab987) which includes the recent fix to 🐛 Splits: Ensure config_ignore works for everyone - set default to functional value Needs review and it does work! (but only after a cache clear). If a setting is both in config_split and config_ignore it will not import in the split specific directory.

Now, drush cex still exports and overwrites the split+ignored value when it shouldn't, but if I recall that's a different, known issue.

Verified that composer require drupal/config_ignore:3.x-dev#96094ab987 solves this issue. I'll watch for that config_ignore next release.

Let me close this.

Thanks for looking into this and closing the issue.

Yes for the export it will only work with splits that use the collection storage. Otherwise config ignore has no way of knowing where the config went.