Ensure that ConfigImport is taking place against the same code base

Created on 3 December 2015, almost 9 years ago

Updated 10 July 2024, 4 months ago

Problem/Motivation

It is important that we people sync configuration is done against the same codebase in both the target and source instance. People have been surprised that you can't sync configuration from Beta-13 to RC-3. This issue will get worse with contrib under active development.

Proposed resolution

When we run update.php write the current versions of the extensions to core.extension. When we install an extension or run updates write the version to core.extension. When we update or install a module store the schema version in core.extension. Use this information to ensure that when we import a full site configuration the codebase and database are in the same state.

Remaining tasks

Review all of the UI text

User interface changes

Additional configuration import validation messages

API changes

None

Data model changes

Additional versions key added to core.extensions. The key holds a list of installed extensions. For each extension the version at install time is stored plus the version the last time update.php is run. For modules, the schema is also stored.

🐛 Bug report

Status

Needs work

Version

11.0 🔥

Component

Configuration →

Last updated about 3 hours ago

Maintained by
🇬🇧United Kingdom @alexpott
🇺🇸United States @tim.plunkett

Created by

🇬🇧United Kingdom alexpott 🇪🇺🌍

Live updates comments and jobs are added and updated live.

Configuration system

Triaged core major
There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.

Needs change record
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment about 1 year ago →
🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Per @catch, this could've prevented 🐛 TypeError: array_intersect(): Argument #1 ($array) must be of type array, string given in array_intersect() (line 203 of .../core/modules/ckeditor5/src/Plugin/CKEditor5PluginManager.php). Postponed: needs info .
Comment 4 months ago →
🇬🇧United Kingdom catch
Bumping this after #3450203: Cannot save Views admin settings due to skip_cache error → which looks like at least two sites on that issue got caught by the same situation (not confirmed yet). This is likely to become more of a problem as config validation gets applied - since config that was previously silently invalid will now be unsaveable in some cases.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024