Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
during the import process, Bad Things may happen.
the only Bad Thing that the configuration system will handle is 'secondary config writes' - for the gory details on that, see #2124535: Prevent secondary configuration creates and deletes from breaking the ConfigImporter.
for any other type of exception, the config system should collect us much information as possible about the error and the state of the import, log them and display them, and stop.
Postponed until
#2416109: Validate configuration dependencies before importing configuration
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedretitling this after discussion today.
Comment #2
mtiftAdded issue number
Comment #3
mtiftComment #4
jhodgdonI think this is config.module, right, not the generic "configuration system" -- you're talking about going to Admin > Configuration Management and doing an import?
Comment #5
xjmWe should postpone this on #2416109: Validate configuration dependencies before importing configuration. Once that issue is in, then we can discuss exactly what we need to do here.
Comment #6
mgiffordOk, that is fixed now.
Comment #7
alexpottWe've got the ability to log errors and display in the config importer - however if they ever occur it means that config validation is missing something. Therefore I'm closing this issue in favour reported bugs in the config import process.