Add Drush command for "upstreaming" configuration

Created on 28 February 2024, 9 months ago
Updated 7 March 2024, 8 months ago

Problem/Motivation

There is currently no "nice" way to move modified or new configuration from the config sync directory to a module (or profile). Instead you have to manually copy the config files over and remove the UUID or manually extract the relevant changes to the respective files. In particular for modified/overridden configuration, we could easily find out where the config originally comes from and offer to "upstream" the local changes into that file.

Proposed resolution

Add a Drush command to upstream configuration. I don't have concrete "designs" for how the command(s?) would work, but right now I am thinking of a single command that is like a wizard that guides you through the different options of what configuration to upstream and where, but that can be controlled by arguments to do the upstreaming directly, so that you don't have to go through the wizard every time. But we'll see.

Feature request
Status

Active

Version

2.0

Component

Code

Created by

🇩🇪Germany tstoeckler Essen, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @tstoeckler
  • 🇬🇧United Kingdom joachim

    > There is currently no "nice" way to move modified or new configuration from the config sync directory to a module (or profile).

    Yes there is! -- in https://www.drupal.org/project/config_devel :)

  • 🇩🇪Germany tstoeckler Essen, Germany

    Fair enough! Thanks for the pointer, haven't looked at Config Devel in ages, that does seem like a real useful companion module for Config Overlay. 👍 Will try it out, but seems to be exactly what I was thinking about from the look of it.

    Will add a note to the project page about that.

    Leaving open for that, for now, and also because I do think it would be nice to have some sort of "automatic" mode without having to specify all configuration explicitly. Especially for project-specific installation profiles, that list is pretty huge and does change somewhat regularly. But nevertheless, very useful hint and maybe such a feature would even be something to consider in Config Devel itself.

Production build 0.71.5 2024