The Drush 'provision-update' command in the 'provision_tasks_extra.drush.inc' file currently has its bootstrap level set to DRUSH_BOOTSTRAP_DRUSH. When using this command, our users have found that the 'drush_provision_tasks_extra_provision_update_pre_validate()' and 'drush_provision_tasks_extra_post_provision_update()' functions that are used by the command lead to the eventual calling of code within the 'provision/Provision/Config/Drupal/Settings.php' file that, when trying to determine the Drupal version of the currently bootstrapped site, comes up with a FALSE value and defaults to Drupal version 6. This causes the site's 'settings.php' file to be re-built for Drupal 6, regardless of the actual version that the site is running under, corrupting the 'settings.php' file.
Setting the 'provision-update' command's bootstrap level to DRUSH_BOOTSTRAP_DRUPAL_FULL fixes this, with the correct version of Drupal being detected.
The attached patch makes this change.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | db_updates_bootstrap_full-issue_#2879209_v2.patch | 585 bytes | kfolsom |
Comments
Comment #2
kfolsom commentedComment #3
colanComment #4
helmo commentedThanks, doing a full bootstrap might be a bit much here though.
Looking at the Drush code it seems like DRUSH_BOOTSTRAP_DRUPAL_ROOT would be enough. Could you verify that?
Comment #5
kfolsom commentedUsing DRUSH_BOOTSTRAP_DRUPAL_ROOT does indeed work. I've updated the patch with this change and have attached it.
Comment #7
helmo commentedThanks, committed.
Comment #8
helmo commented