- Issue created by @batigolix
- Assigned to jurgenhaas
- 🇩🇪Germany jurgenhaas Gottmadingen
Thanks @batigolix for reporting this. We've never used collections for this ourselves, so that's why we've missed it during implementation. I'll assign it to myself and hope to find some time to look into this.
- 🇳🇱Netherlands batigolix Utrecht
Thanks @jurgenhaas for the feedback.
I'd like to add that for me this has very low priority. I could even switch back Config Split to the other storage mode.
- 🇩🇪Germany jurgenhaas Gottmadingen
I've looked into this, and it turns out that we're polling all the config split directories to find out which config entity belongs to which split. That fails when you configured a new split but never exported that. That's why the directory doesn't exist yet.
There must be another way to find out, whether a config entity belongs to a split and to which. I've raised that question in 💬 API question: find split for given config entity Active and need to wait for their feedback.
- Issue was unassigned.
- 🇩🇪Germany jurgenhaas Gottmadingen
Unfortunately, it is not that simple, to find out to which collection a config entity belongs to. Without that knowledge, CAE can't really do its job. So, I guess we're down to only supporting collections where the config entity file already exists in the collection's storage.
For more details, please refer to the related issue.