This may appear to be a noob problem, but perhaps I'm using the module wrong.

  1. I am on local. I have uninstalled the purge module, which should be installed on production.
  2. I install config filter and config ignore with drush.
  3. I run drush cex. I note a setting has been modified which I do not wish to be modified: purge_queuer_coretags.settings
  4. I paste 'purge_queuer_coretags.settings' into config ignore settings
  5. I run drush cr
  6. I run `drush cex` again, but purge_queuer_coretags.settings is still included in the export.
  7. I try adding 'purge_queuer_coretags.*' to the settings, but that doesn't work either.

What am I doing wrong? Am I misunderstanding something about the workings of this module?

$drush --version
 Drush Version   :  8.1.11 
$

Comments

glass.dimly created an issue. See original summary.

glass.dimly’s picture

glass.dimly commented
Issue summary: View changes
tlyngej’s picture

tlyngej commented

Hi @glass.dimly

Just for clarification, does the config ignore module kick in, if you try to ignore any other config name? Like system.site.

glass.dimly’s picture

glass.dimly commented

I tried a few other ones, I made a list of all the ones I wanted to ignore, there were several, none worked. Now I've moved on to config_split though.

glass.dimly’s picture

glass.dimly commented
Title: Module appears to do nothing » Add cache clear to docs
Component: Code » Documentation
Category: Bug report » Task

Alright, this was my fault, I installed and tried again.

I didn't cache clear after I added settings.

Since this is required, can this be added to the docs?

tlyngej’s picture

tlyngej commented

Right. I've manged to re-produce the issue (I think) so that's step one completed.

Thanks for reporting this @glass.dimly!

tlyngej’s picture

tlyngej commented

After doing some testing I'm fairly sure that this could not be fixed by clearing cache.

I can re-produce the issue by doing following (config folder is one level above):

drush si minimal -y
drush en config_ignore -y
drush cex -y
cat ../config/sync/system.site.yml
drush cset -y system.site name 'Config Ignore'
drush cset -y config_ignore.settings ignored_config_entities.0 'system.site'
drush cex -y
cat ../config/sync/system.site.yml
drush cset -y system.site name 'Config Ignore Changed'
drush cex -y
cat ../config/sync/system.site.yml

The above will try to export and output the system.site configuration three times.
First time, the name is Site-Install, second time it's Config Ignore, and likewise the third time.

Note how the system.site configuration was setting to be ignored before the second export, and therefore should have been left as Site-Install in all three cases.

So, that proves that there is an issue.

However, if I move the drush cset -y config_ignore.settings ignored_config_entities.0 'system.site' bit before the first export, the rest of the exports works as expected (are ignored).

  • bircher committed 135ec3d on 8.x-2.x 
    Issue #2889769 by bircher: clear config filter cache on ignore form...

bircher credited bircher.

bircher’s picture

bircher
Location 🇨🇿
commented

I am not sure what exactly the issue is, but I added cache clearing to the ignore form submission just in case.
We still might need to improve the documentation. Of course the active config_ignore settings are used for filtering so if the config ignore setting is updated as part of the deployment the the newly ignored config will not be ignored in that deployment. a single import of the ignore settings first would solve that.

bircher’s picture

bircher
Location 🇨🇿
commented

ah! reading the issue summary again I see what the problem is. We currently do not ignore config on export if I am not mistaken. Seeing that this is something that might be expected we could add an option to ignore also on export.

If you want to not export you can currently use config_split. If you configure the split with an empty folder it will export it to a database table and so not export it.

tlyngej’s picture

tlyngej commented

@bircher Config is ignored upon exporting.

But would have been lovely if that was all :-)

tlyngej’s picture

tlyngej commented
Status: Active » Closed (works as designed)

Right, this has come down to me not really know how Config Filter (which this module relies on) works.

Turns out that Config Ignore don't support exported configuration.

But I certainly intend to change that!