- Issue created by @fago
- 🇨🇭Switzerland bircher 🇨🇿
Hi fago
I have reviewed the issue you linked and the project you had this problem with.
It is a very interesting project, so I am inclined to help you out.
But I came to the conclusion that you are bypassing the import and export config transformations.
Your module transfers versions of the active config between different environments. The "big" CMI2 innovation from Drupal 8.8 was that we have the import and export transformations that happen to a storage before respective after the config storage is passed between environments. Traditionally that is with git and the ../config/sync directory that the sync storage writes to. In your module you invent a new transport layer for the "sync storage". But you don't do the import and export transformations ( by using the export storage and the import storage transformer services → ) so actually you add a transport for a version of the active storage.
So in a way you are adding another paradigm and I don't understand why. So I am not inclined to support that with Config Ignore.
If you want a visual illustration check page 15 of my devdays 2019 slides. You can replace the active storage with a snapshot and the sync storage with the transport layer you invented.
