Don't use -y automatically on drush commands, fixes #1118, fixes #455 #1120
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.
The Problem/Issue/Bug:
We have long defaulted to the drush -y, assuming people were using
ddev exec
or an exec hook, but it makes people crazy when they use drush inside the container.How this PR Solves The Problem:
Manual Testing Instructions:
ddev ssh
and trydrush sql-drop
. It will ask first.ddev exec drush sql-drop
and it will just drop the db with -y.Automated Testing Overview:
Related Issue Link(s):
OP #1118 and #455