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

beejeebus’s picture

Title: how should we handle exceptions during configuration import? » stop config import and log/display error and state information as best we can
Issue summary: View changes

retitling this after discussion today.

mtift’s picture

Issue summary: View changes

Added issue number

mtift’s picture

jhodgdon’s picture

Component: configuration system » config.module

I think this is config.module, right, not the generic "configuration system" -- you're talking about going to Admin > Configuration Management and doing an import?

xjm’s picture

Issue summary: View changes
Status: Active » Postponed
Related issues: +#2416109: Validate configuration dependencies before importing configuration

We 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.

mgifford’s picture

Status: Postponed » Active

Ok, that is fixed now.

alexpott’s picture

Status: Active » Closed (won't fix)

We'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.