2

I am taking over a site that was built without configuration management, I installed the configuration module for the first time (I am used to using features). I am wondering if it is bad practice to just select all in all the categories and track all the available configurations instead of trying to cherry pick the applicable ones. What are the effects of performance, etc.

3

I have tried it in Drupal7 (not on Drupal8).

Logically it should be good practice to track all the configurations. However, not all the "configurations" are actually configurations. For example there are persistent variables or cached values that have nothing to do with the configuration. So, tracking all of them would undermine the aim of configuration tracking.

Besides this, the UI becomes infinitely slow and unresponsive when you select all the configurations. I guess it is because it tries to find out dependencies of each configuration and does it in an inefficient way. You can try to handle them from the command-line (with drush) but I doubt that it would be more efficient.

So, I think that the best option is to cherry pick the relevant configurations. But once you start cherry-picking them, you might as well use features, configuration management loses its meaning.

This is basically what I did on a project of mine: I started with configuration management, and ended up using features, which by the way was a tedious process.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.