- π¬π§United Kingdom therobyouknow
Responding to comment #2, https://www.drupal.org/project/config_split/issues/2967961#comment-12595863 β¨ Option to remove UUID and Config Hash on export Closed: won't fix
I think there is a case for removal of UUID and Config Hash on export: publishing Drupal distribution source code. Here, UUID and Config Hash aren't relevant.
Now, I know distributions are to be superseded by Drupal recipies - but that is still in development. There are some very successful distributions: farmos.org and LocalGovDrupal. I've browsed through some of the FarmOS config code and observed that UUID and Config Hash are absent.
Indeed, I am advised that, when publishing code updates, the LocalGovDrupal team manually remove UUID and Config Hash from export
https://www.linkedin.com/feed/update/urn:li:activity:7213504134296076289...
See also tools to automate removal.
https://drupal.stackexchange.com/questions/295320/best-practice-remove-u...Distributions still have mileage and are an important part of promoting the Drupal ecosystem. Standard, automated support to make config non-instance specific by removing this UUID and Config Hash would be welcome.
- π¨πSwitzerland bircher π¨πΏ
There is a case for removing the uuid and the default hash of course, but that is to create default config for a contrib module. That is has nothing to do with a config import or export between different environments of the same site. And as such it has nothing to do with config split.
Config Distro is meant as an alternative to the config import/export for maintaining distributions. I would argue that you should create a small module that does this with the config distro events.