We need to support the use-case when site configs are changed from Drupal admin interface so that they are not reset/overridden by next deploy. Currently we have the drush config-import command executed on every deploy.
I've seen it done using the following approach:
when developer is working on a task he creates special code to import only the configs he created / deleted / updated for this task (hook_update N())
there is no drush config-import command execution on deploy; only the code from hook_update_N() is run to perform operations on configs
then (after every deploy) there should be config-export command execution and commit of all the config changes (from production site only) into the repository
For the partial configs import from code we can use the https://www.drupal.org/project/confi module or maybe some other approach which supports partial config changes.
Here are the examples of configs that would benefit from it:
We need to support the use-case when site configs are changed from Drupal admin interface so that they are not reset/overridden by next deploy. Currently we have the
drush config-importcommand executed on every deploy.I've seen it done using the following approach:
drush config-importcommand execution on deploy; only the code from hook_update_N() is run to perform operations on configsFor the partial configs import from code we can use the https://www.drupal.org/project/confi module or maybe some other approach which supports partial config changes.
Here are the examples of configs that would benefit from it: