#5952: Database update step for drush deploy behaves differently than drush updb --no-cache-clear
#5953
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes the issue drush-ops#5952
|
I think that makes sense. |
|
Can this run without boostraping and no kernel - the site the commands operate on is potentially having significant change. This command really should try to load as little from it as possible. |
|
That sounds really useful and easy to accomplish. I'll push that change today. |
|
Merged, and backported to 12.x |
|
@weitzman thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the issue #5952
As a reminder, Drush's usage of UpdateKernel started in #5953. This PR would again use it in the main request of deploy command, in addition to deploy's subrequest to updatedb.