Exclude configuration from import/export I thought this was a simple use case of the new Configuration management system, but I haven't had any luck finding out how to solve this:

Problem

I want to store configuration in git and use drush to export configuration during development and then on deployment import the configuration. Pretty similar to doing a features revert in Drupal 7. My problem is that I don't want to store access codes in git for various integrations. This results in these configurations being deleted on
$ drush cim -y

Where I looked

I was hoping there would be a simple list/configuration for configs that should be excluded on import/export. It seems there was at some point but it must have been removed again, since it's available at present Drupal 8 release.

I looked into how config changes are being made comparing the active and sync storange to see if there as a place where I could remove changes, this didn't seem to be the case.
I looked at how drush does the configuration import as it has some configuration excludes of it's own, but it didn't look like this was extensible.
I looked at ConfigEvents, but these all seem to happen after an import, so doesn't look like this can be used.

Am I missing something, or is it not possible to simply exclude configs from import/export?
You can use the &quot;Config Ignore&quot; module: https://www.drupal.org/project/config_ignore

Ever experienced that your site's configuration was overridden by the configuration on the filesystem, when doing a drush cim?
Not anymore!
This module is a tool to let you keep the configuration you want, in place.