We've had some deployment issues where the config_import_single commands imported a couple of single config files, which later weren't recognized by the main config-import command.

After some investigation, I've found that there were some differences between what the module does and what core's ConfigSingleImportForm does. The provided patch fixes that by introducing batch API to the import.

Issue fork config_import_single-3236725

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jzavrl created an issue. See original summary.

jzavrl opened merge request !2

jzavrl’s picture

jzavrl CreditAttribution: jzavrl at Dropsolid commented
Status: Active » Needs review

Provided MR also includes a call from configFactory->reset().

  • daften committed 3bd6343 on 1.0.x authored by jzavrl 
    Issue #3236725: Bring the import logic in line with core's...
daften’s picture

daften CreditAttribution: daften at Dropsolid commented
Status: Needs review » Fixed

Seems to work well, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.