Option to run drush tasks synchronously; block drush exit until task is completed

[jessepinho]

When I deploy code, my process looks like the following:

• Authorize with Pantheon: drush pauth
• Clone my live environment to test: drush psite-clone -y drush psite-uuid my-site live test
• Back up the live environment: drush psite-backup drush psite-uuid my-site live
• Deploy code from dev to test: drush psite-deploy -y drush psite-uuid my-site test --update
• Run tests on the test site
• Assuming all tests passed, deploy code from test to live: drush psite-deploy -y drush psite-uuid my-site live --update

I'd love to write a script that does all of this for me in this order. The problem is, commands like drush psite-clone initiate the cloning job and then exit, which means a script that does all of the above could theoretically deploy to my live environment before the cloning/backing up/testing/etc. have actually completed. Would it be possible for there to be an option like --no-async where a command does not exit until the backup/etc. has actually been completed? And it should return an error code if the job fails, so that the next step wouldn't ever get executed (the commands in my script would be chained together with &&).

[joshkoenig]

This makes a lot of sense and should be something we can support.

There's currently under-the hood work in progress on the platform that should improve our tooling around tracking the status of individual jobs.

We'll definitely that this as a valid feature request. Thanks for sharing your use-case!

[forssto]

+1 on this. Getting downstream db pulls scripted in synchronous shell scripts is an absolute must for any professional Drupal CI environment.

Looking forward to this rolling out.

[mikevanwinkle]

this is related to issue https://github.com/pantheon-systems/terminus/issues/143