cannot use 'drush upwd' to create a password containing spaces

[byrond]

Not sure if this is anecdotal or not, but running the-vagrant on Ubuntu 16.04.1, I can't set a password containing spaces using drush. It works fine through the UI. For example:

drush user-password admin --password="correct horse battery staple"

Note: the command above claims it succeeds, but attempting to login with the password fails. Setting a password that contains no spaces using the command above works correctly.

[becw]

Does this work with drush on other environments?

[byrond]

@becw I seem to remember it does work on other environments, but I will double-check and report back. I will also make sure I can reproduce the issue on the-vagrant since it has been a while since I reported it.

[becw]

I think this affects drush sqlq and drush php-eval as well. @damontgomery found that it was related to the drush wrapper script installed by the-vagrant: https://github.com/palantirnet/the-vagrant/blob/develop/bin/the-vagrant-installer

It may be possible to remove this wrapper now that we add vendor/bin/ to the $PATH -- which is very convenient but still somewhat blunt, IMO, since what happens when you're running multiple projects on the same machine? We often do this when migrating from a D6 or D7 site to a D8 site.

[damontgomery]

Can drush launcher be installed and added to the path? That should find drush in the vendor folder.

…

On Wed, Jun 27, 2018, 4:34 PM Bec White ***@***.***> wrote: I think this affects drush sqlq and drush php-eval as well. @damontgomery <https://github.com/damontgomery> found that it was related to the drush wrapper script installed by the-vagrant: https://github.com/palantirnet/the-vagrant/blob/develop/bin/the-vagrant-installer It may be possible to remove this wrapper now that we add vendor/bin/ to the $PATH <https://github.com/palantirnet/the-vagrant/blob/develop/conf/vagrant/provisioning/roles/common/tasks/main.yml#L34-L36> -- which is very convenient but still somewhat blunt, IMO, since what happens when you're running multiple projects on the same machine? We often do this when migrating from a D6 or D7 site to a D8 site. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAYSTlj8ESw6U2rHgSXaTpR-quqoo64Oks5uA_psgaJpZM4NRBvf> .

[becw]

I wonder if it would make more sense to copy the drush.wrapper script from the drush examples and use that to specify our drushrc.php -- since that's the unique thing this script is doing. As you point out, Drush itself will handle the other part of this (finding the project-specific drush).

In the meantime, this PR #53 also solves this issue.

[damontgomery]

I'm not sure if this helps, but I found the following about drush.yml as a replacement for drushrc.php in Drush 9. drush-ops/drush#3027

[becw]

I've merged #53 as a fix for this issue. It will be included in the next release.