-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database update step for drush deploy
behaves differently than drush updb --no-cache-clear
#5952
Comments
Fixes the issue drush-ops#5952
drush deploy
behaves differently than commands it is replacingdrush deploy
behaves differently than drush updb --no-cache-clear
This may be the reason why some devs recommend running During testing of the change we've spotted that |
#5953 fixed this |
Describe the bug
We use
drush deploy
in our CI, however recently we had two deploy failures. The most recent one beingsimple_sitemap
module changing its services definition. In both cases database update step indrush deploy
executed in a different way thandrush updb --no-cache-clear
it is trying to create a shortcut for.To Reproduce
drush si
to install it.composer require drupal/simple_sitemap:4.1.8
and enable it usingdrush en simple_sitemap
.composer require drupal/simple_sitemap:4.1.9
.drush deploy
.Expected behavior
The command should've updated the database and imported the configs successfully.
Actual behavior
Immediately received an error:
Workaround
If you run
drush updb --no-cache-clear
instead, it will complete database updates successfully. Then you can run other commands in order with no issues.System Configuration
Additional information
Adding
#[CLI\Kernel(name: 'update')]
annotation fromdrush updb
todrush deploy
command solves the issue.The text was updated successfully, but these errors were encountered: