I tried adding migrate_plus.migration.* under "Configuration entity names to ignore", but I still get "Differences of the active config to the export directory:" from my migrations after running drush config-export ...

Two other issues:

  1. I am getting this warning, when I access the settings page, before adding and saving an entity name:

    Warning: implode(): Invalid arguments passed in Drupal\config_export_ignore\Form\SettingsForm->buildForm() (line 38 of modules/contrib/config_export_ignore/src/Form/SettingsForm.php).

    Drupal\config_export_ignore\Form\SettingsForm->buildForm(Array, Object)
    call_user_func_array(Array, Array) (Line: 518)
    ...

  2. Shouldn't the menu be put under Development, and not System?

Comments

ressa created an issue. See original summary.

mohit_aghera’s picture

mohit_aghera commented

Hello @ressa
This module is created to make config export ignore when we use config_split and we are exporting via particular config split.
You can try by drush csex command, it shouldn't give the issue.

Also, as per the recent migration API changes, we no longer need migrations as config entity.
You can write in your module's migration directory and it won't be imported as configuration.
For ex: if your module name is "content_import" then migration files can be kept here at "content_import/migrations" directory.
That way, you won't have to worry about dealing with migration on config export.

ressa’s picture

ressa
he/him
commented
Status: Active » Closed (works as designed)

Thanks for your fast reply @mohit_aghera. I now realize it says "This module allows to ignore specified configuration entities from being exported by config split" on the module page, which of course means that config split should be used. So I could have just read it more thoroughly.

And thank you so much for sharing the tip about moving migrations from content_import/config/optional to content_import/migrations. Like you wrote, migration config files don't get included after drush config-export that way, which was exactly what I was looking for, and even without having to add any modules, great!

Can you guide me to a page in the Migrate API documentation, where this new feature is described?