Document the reason why recipes don’t import a module’s config entities by default

It is already the case that, in recipe.yml, you HAVE to say what to do with the config of each module your recipe installs. There is even validation code for it.

I believe on points 2 and 3 it should note that this means you are overriding the default module installation and point out the possibility of unwanted affects

Should be added to:
https://git.drupalcode.org/issue/distributions_recipes-3381259/-/blob/33...

We also decided that we could use NULL to bring in only the module's simple config. That should be tested and documented.

Adding to the IS to mention that config actions are able to modify any module config imported. I still personally believe that this speaks to importing all module config as a best practice, but have this discussion document is tremendously helpful.

thejimbirch → changed the visibility of the branch 3454444-document-the-reason to hidden.

thejimbirch → changed the visibility of the branch 3454444-author-guide to hidden.

thejimbirch → credited guptahemant → .

thejimbirch → credited Prashant.c → .

Thanks for the great reviews! Merged.

Automatically closed - issue fixed for 2 weeks with no activity.