Skip to content

fix: offer Drupal's Import config only when there is config to import - #90

Merged
geodro merged 1 commit into
mainfrom
fix/drupal-import-config
Sep 25, 2026
Merged

geodro merged 1 commit into
mainfrom
fix/drupal-import-config

Conversation

@geodro

@geodro geodro commented Sep 25, 2026

Copy link
Copy Markdown
Member

A fresh Drupal has no exported configuration, and drush refuses to import an empty sync directory because applying it would delete the site's configuration. lerd setup --all runs every setup step, so on a new Drupal project it aborted at Import config right after the installer had succeeded, which is how the release test run found it.

Import config is now offered only once config/sync holds an exported site, in each Drupal definition and in the drush package alike. A file check is a key every binary already reads, so older installs pick this up as it is.

A fresh Drupal has no exported configuration, and drush refuses to import an empty sync directory because it would delete the site's configuration. lerd setup --all runs every setup step, so it aborted on every new Drupal project right after the installer had succeeded. The step is now offered only once config/sync holds an exported site, in the Drupal definitions and in the drush package alike.
@geodro
geodro requested a review from a team as a code owner September 25, 2026 15:02
@geodro
geodro merged commit c16629e into main Sep 25, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant