This module provides a framework for providing patch files for config (the differences between active configuration and sync configuration). For a site built out from source files, this allows sitebuilders to make changes to configuration in the UI and push a button to create a patch which may then be committed back to source. The framework is extensible, so additional output plugins may provide integrations with e.g., cloud source control providers.
Since patches reference file paths, the path of these files is configurable. In other words, if your synchronized config is stored in drupal/config in your source repo, you can configure drupal/config as your base config path in config_patch.
When installed, config_patch provides an additional tab Patch on the admin config synchronization pages listing config that is out of sync and providing a button to output the patch in various forms. It also adds a link in the admin toolbar showing the number of config items that differ between active and sync storage.
Project link
https://www.drupal.org/project/config_patch
Git instructions
git clone --branch '8.x-2.x' https://git.drupalcode.org/project/config_patch.git
Comments
Comment #2
avpadernoThank you for applying! Remember to change status, as in this queue the Active status says to reviewers they need to wait before reviewing the project, as it's not yet ready.
Comment #3
ahebrank commentedComment #4
poorva commentedHi Andy,
Pareview is showing many coding standards and read me issues. Please fix all of them and then again change the status to "needs review".
Comment #5
vipin.mittal18Hello Andy,
License "GPL-2.0+" is a deprecated SPDX license identifier. use "GPL-2.0-or-later" instead in your composer.json.
Thanks
Vipin Mittal
Comment #6
ahebrank commentedI've updated to clear out some of the style issues.
I'm going to leave the Drush command annotation alone. I'm following Drush's example here (e.g., https://github.com/drush-ops/drush/blob/10.x/src/Drupal/Commands/core/En... so I don't want to mess with it and break Drush's parser).
Comment #7
damienmckennaWhile there are a few coding standards issues to tidy up, the module is quite well built, including the "restrict access" option on the permission.
Comment #8
damienmckennaComment #9
damienmckennaThanks for your contribution, Andy!
I updated your account so you can opt into security advisory coverage now.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on Slack or IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the reviewer(s) as well.
Comment #10
ahebrank commentedThanks, Damien!
Comment #11
avpaderno