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
--yes and --no-interaction do not behave identically #3082
Comments
Hm, I prefer the behavior you describe. If this is repeatable, we should change the docs. This is handled here: https://github.com/drush-ops/drush/blob/master/src/Style/DrushStyle.php#L14 Symfony defines --no-interaction as "answer all questions using the default value". The downside of replicating this behavior everywhere is that So, lets fix the docs. |
I think this is a happy accident that may need to be fixed. Specfically, look at how we set the value of DRUSH_NEGATIVE at drush/src/Preflight/LegacyPreflight.php Lines 103 to 114 in 3a6d8d7
This overloading of --no-interaction is going to bite us later, no? |
See #3084 where I stop overloading -n|--no-interaction and also modernize a bit |
Lets discuss in #3084. |
I'm using Drush 9.0.0-beta7.
According to docs, previous comments, and this issue, the
--yes
and--no-interaction
options should behave identically. In practice, they do not, at least for the site install command.drush si --yes
installs a site without any further interaction from the user, because it assumes a 'yes' response to whether to drop the database prior to installdrush si --no-interaction
fails because it assumes a 'no' response to whether to drop the databaseIronically, for the moment this is actually a good thing, because if both of these were to behave like
--no-interaction
and assume 'no', there would be no way to force a site install! But we definitely need to figure out what the intended behavior is here.The text was updated successfully, but these errors were encountered: