- Issue created by @daffie
- 🇳🇿New Zealand quietone
did you mean 11.x? Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
The database driver for MongoDB needs to be able to override config items with its ones that are specific to MongoDB. The 2 main problems are:
1. When this database driver makes a change on a config item, the database driver's module will be added as a dependency. When such a config item is used in a recipe, recipe will fail. This is because the recipe will check every config item to see if there are changes between the loaded config item and the config item from the yaml file. The added dependency to the mongodb module will make this check fail.
2. Every view is a config item. A view is database query that has been build with a GUI. The tables on which the query is build are different for relational databases and for MongoDB with its entity storage in JSON objects. Therefore is the config item for the same view different for a relational database and the one for MongoDB.
Profiles are able to override config items. This issue will allow the default database driver to do the same.
Allow the default database driver to override config items from module, themes and profiles. Let the module that is providing the default database driver store the overridden config items in the directory MODULE_ROOT/config/overrides
For example:
MODULE_ROOT
> config
> overrides
> dblog
> optional
> views.view.watchdog.yml
> media_library
> install
> views.view.media.yml
TBD
None
None
The default database drivers module can override config items just
None
TBD
did you mean 11.x? Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .