You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A colleague and I wasted non-insignificant time trying to debug a problem that was the result of a misunderstanding of drush deploy behavior, due to something it outputs while running (and maybe a little ignorance of a certain shell command). If there are config diffs when running drush deploy, it will output Import the listed configuration changes? (yes/no) [yes]:, and sometimes the actual import takes a while, so it can appear to be waiting for your response (like a normal drush cim).
I guess she was unaware that deploy assumes -y or --yes if only one waits. I've also gotten tripped up by this on occasion, but must have typed y out of habit, whereas she typed in a full yes. This resulted in her terminal outputting hundreds of thousands of lines of the letter y in a matter of seconds, because apparently that's the default behavior of the *nix yes command (which I only had the most passing familiarity with before today, only in a scripting context, so didn't realize sooner what the problem was).
Describe the solution you'd like
Don't output Import the listed configuration changes? (yes/no) [yes]: while drush deploy is running, at least for the default/non-verbose mode. Or maybe it's just recycling what cim outputs (it's indeed the same exact text, barring --no usage) in which case it needs more forceful prevention/suppressing somehow?
Also, change the example in drush deploy --help to not use -y (and to remove and accept all prompts), since it implies that's not already the default behavior.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A colleague and I wasted non-insignificant time trying to debug a problem that was the result of a misunderstanding of
drush deploy
behavior, due to something it outputs while running (and maybe a little ignorance of a certain shell command). If there are config diffs when runningdrush deploy
, it will outputImport the listed configuration changes? (yes/no) [yes]:
, and sometimes the actual import takes a while, so it can appear to be waiting for your response (like a normaldrush cim
).I guess she was unaware that
deploy
assumes-y
or--yes
if only one waits. I've also gotten tripped up by this on occasion, but must have typedy
out of habit, whereas she typed in a fullyes
. This resulted in her terminal outputting hundreds of thousands of lines of the lettery
in a matter of seconds, because apparently that's the default behavior of the *nixyes
command (which I only had the most passing familiarity with before today, only in a scripting context, so didn't realize sooner what the problem was).Describe the solution you'd like
Don't output
Import the listed configuration changes? (yes/no) [yes]:
whiledrush deploy
is running, at least for the default/non-verbose mode. Or maybe it's just recycling whatcim
outputs (it's indeed the same exact text, barring--no
usage) in which case it needs more forceful prevention/suppressing somehow?Also, change the example in
drush deploy --help
to not use-y
(and to removeand accept all prompts
), since it implies that's not already the default behavior.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: