Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When trying to setup a database server through drush like I did with 6.x-1.9 then I get the error, "Unknown option: --master_db" and I don't see any alternatives in 'drush help provision-save'. In irc ergonlogic noticed, "it's been removed from db.drush.inc... hmm, now it's in db/Provision/Service/db.php"
Comment | File | Size | Author |
---|---|---|---|
#2 | provision_save_missing_options-1972286-3.patch | 1.22 KB | trrroy |
#1 | provision-drush_master_db-1972286-2.patch | 1002 bytes | trrroy |
Comments
Comment #1
trrroy CreditAttribution: trrroy commentedThe attached patch is working for me. Now I can use:
drush provision-save @server_192168123123 --context_type=server --remote_host=192.168.123.123 --db_service_type='mysql' --master_db='mysql://aegir:123pwd@192.168.123.123'
Comment #2
trrroy CreditAttribution: trrroy commentedI also found some other options related to web packs are missing in 2.x, --master_web_servers and --slave_web_servers. Here's an update to this patch to add those too.
Comment #3
anarcat CreditAttribution: anarcat commentedComment #4
anarcat CreditAttribution: anarcat commentedi don't think this is the right way to do this.
normally, those parameters are set directly in the service subclass. in #1784108: pack (and cluster?) modules incompatible with SSL i have a similar issue, and i tried to fix this the "right way", but it failed, see commit 7a86f47 in provision.
those parameters should really propagate upwards, and they don't, and that's a bug that's blocking other functionality so i'm marking this as critical.
Comment #5
Steven Jones CreditAttribution: Steven Jones commentedGiven the nature of the provision-save command, maybe we should just allow any option to be sent.
We can do this by specifying the
'allow-additional-options' => TRUE
in the Drush command definition.Comment #6
anarcat CreditAttribution: anarcat commentedSo I did that, but it seems to me this should be better implemented in the hook_command. I'll open a separate issue about this: #2009408: missing documentation for sub-classes of Provision_Context_*