In #2017189: Option validation skipped for --backend requests '--invoke' was eliminated in favour of '--strict=0'. We'll need to change this in our code if we want to support Drush 6.x. Does anyone see any reasons that '--strict=0' wouldn't work for us?
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | hosting-fix_invoke_flag-2038891-2.patch | 583 bytes | jwjoshuawalker |
| #1 | hosting-fix_invoke_flag-2038891-1.patch | 2.14 KB | ergonlogic |
Comments
Comment #1
ergonlogicIt looks like just switch from
'invoke' => TRUEto'strict' => FALSEin the 3 places we do this should be sufficient. See attached patch.Comment #2
ergonlogicActually, I got this error when attempting to install a site:
So, we can either add 'client_email' as an option to 'provision-install-backend' (which I think is the correct solution):
Or we could call
provision_backend_invoke()with--strict=0:Comment #3
anarcat commentedIs this backwards-compatible with drush 5?
I agree that adding client_email to -backend is the right way.
Comment #4
ergonlogicYes, it's compatible with Drush 5.
Fixed in f488709 for Hosting, and c8febbc in Provision.
Comment #5
ergonlogicno, really, fixed!
Comment #7
jwjoshuawalker commentedclient_email option also needs to be added to provision-import or you get the same error.
Patch attached for latest 6.x-2.x
Comment #8
jwjoshuawalker commentedInteresting.. I also just got it on a verify task. It had verified the same site twice before without running into that, but this last time it ran the command:
The only option I see in provision-verify is: working-copy
Comment #9
anarcat commentedcommitted, thanks.