- Status changed to Closed: won't fix
6 days ago 12:43pm 2 September 2024 - 🇺🇸United States thejimbirch Cape Cod, Massachusetts
Since it has been decided we are not tracking recipe application, I am going to close this as Won't fix.
With recipes in the mix, there are (at least) three possible update paths for extension-provided config: two that are currently supported in Drupal and a third that's new with recipes.
1. None. Once a module's configuration is installed, it is never updated. Any configuration added to a module after that module was installed is never installed (barring some edge cases involving optional config). This is the current default behaviour.
2. Full. When a module is updated, all previously-installed configuration that it provides is updated and any newly provided config is installed. Currently this can be achieved with the use of contrib modules:
Update Helper →
or
Config Distro →
+
Configuration Synchronizer →
.
3. Partial. When a module is installed via a recipe, any extension-provided config installed by the recipe is on an update path, but any config added to the module afterwards is never installed.
Directly supporting updates is out of scope for recipes per se and will be addressed via other open issues. But we should ensure at this point that such an update solution has the tools it would need to support update strategies.
ExtensionList::getExtensionInfo(), such as full_config defaulting to 1 (TRUE).And/or provide a method to directly determine whether a wildcard was originally used.
This gives an update solution the information it needs to support multiple update strategies.
Closed: won't fix
11.0
Documentation
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Since it has been decided we are not tracking recipe application, I am going to close this as Won't fix.