Option to remove UUID and Config Hash on export

Created on 30 April 2018, over 6 years ago
Updated 8 July 2024, 6 months ago

An option to remove UUID's and Config Hash from exported configurations would be a desirable feature. This would enable the ability for Splits to be installed on non-originating sites.

A similar option would be Drupal Console's config export solution via drupal config:export --remove-uuid --remove-config-hash.

My personal need stems from the desire to replace Features (currently removes UUIDs by default). I several sites with identical configuration. However, these sites have uuids set differently for each piece of configuration because the feature modules were installed from a module install (config/install) process rather than configuration sync. In order to import split configuration (or any) I have to manually remove uuid/hash to import.

✨ Feature request
Status

Closed: won't fix

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States brandonratz

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¬πŸ‡§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.

Production build 0.71.5 2024