How to export the config files of a content type to a module?

Question

I have a custom module. I created a content type and added some fields to that content type. I also enabled the layout builder on the manage display of the content type

Then I run drush -y cex to export the config files.

Then I copy all the config files related to my content type to the module's config/install director

Now if I make some changes to content type, their config files should be added/updated/exported in/to the module's config/install directory and should not be added to the site's default sync directory.

Is this possible?

Answer 1

You can use a Drupal Console command:

drupal config:export:content:type page \
  --module="demo" \
  --optional-config \
  --remove-uuid \
  --remove-config-hash

Source: https://drupalconsole.com/docs/en/commands/config-export-content-type

Answer 2

You can do exactly this with the Features module.

Features provides a UI and API for taking different site building components from modules with exportables and bundling them together in a single feature module. A feature module is like any other Drupal module except that it contains additional information in its info file so that configuration can be checked, updated, or reverted programmatically.

While ignoring the related config from configuration management with Config Ignore at the same time. Which also takes wildcards so you don't have to enter every single config object by hand.

Answer 3

You maybe misunderstand the drupal configuration workflow. A modules config files will only be installed when installing the module. At that moment the configuration will be imported in the database, and so, when you export the sites configuration your modules config will also be part of that. Subsequent changes to configuration of your own module can be done in update_hooks, but it's easier to make changes on the site self, export that, and have it versioned in that site's repo. If your module only holds config, you could also uninstall it immediately after you installed it, because it doesn't serve a purpose anymore.

So doing this, exporting config to a module, makes sense when you need that same configuration on another site that doesn't already have that configuration. Its a quick way to setup parts of the site the way you like. If a customer wants events where users can register to, and you created that before, you could create a module for that, that when enabled on the site sets up the basics for it. Further customizations to the clients wish on that particular configuration will be versioned in its own repo, when exporting the sites configuration.

Answer 4

After installing the Configuration Split module, the configuration can be exported in one or more "splits", enabling you to target different configurations for different environments or situations.

1. Install the Configuration split module :

   composer require drupal/config_filter drupal/config_split && drush en -y config_filter config_split

2. Using the Backoffice create 2 splits one will export your module configurations to config/install and the other will export other configurations into standard sync folder, a split enables you to :

   • Specify the exportation directory ex (config/install).
   • Specify what module configuration to export (your module).

3. just run drush csex -y and the code will be exported according to the split setup.

you may find these videos useful: https://www.youtube.com/results?search_query=Configuration+split+module+