Change site database password?

Would be nice to have.

It relates a bit to: #1132512: [meta] Manage databases as separate entities

It could also start as something in http://drupal.org/project/hosting_tasks_extra

Provision_Service_db_mysql::grant and Provision_Service_db_mysql::revoke methods already exist. Since site db credentials are stored in the vhost and the site drushrc.php, those are where we'd need a re-write, not settings.php.

You probably want something like:

$config = new Provision_Config_Drushrc_Site(d()->name);
$config->db_passwd = $new_password;
$config->write();

With that, I think you can just verify the site to have the vhost re-created with the new credentials.

@cweagans, I think helmo's suggestion in #1 is good. tasks_extra is becoming our incubator for potential additions to aegir core .

also, keep in mind this actually happens at every migrate.

i don't think we should have this that late in the 2.x release cycle, but it's welcome in contrib or 3.x.

@cweagans, I know you'd posted a gist or something with some code snippets at one point. Posting a patch to this issue would probably make things simpler though.

We'll be on IRC this week too.

okay, so what's not working in that command?

I think I got it working....
https://gist.github.com/helmo/a564e718715787a0287f/revisions

diff --git a/provision_change_site_password.drush.inc b/provision_change_site_password.drush.inc
index 567e0d7..68c37ad 100644
--- a/provision_change_site_password.drush.inc
+++ b/provision_change_site_password.drush.inc
@@ -54,6 +54,9 @@ function drush_provision_change_site_password() {
       }
     }
 
+    // save new password to our context, other code needs it to e.d. render the vhost config
+    drush_set_option('db_passwd', $new_password, 'site');
+
     // Update the site context and trigger a verify to rewrite all related
     // Apache virtualhosts.
     $config = new Provision_Config_Drushrc_Site(d()->name);

A comment in generate_site_credentials() already mentions that this is not the best way to handle variables....

let's mark this as postponed until we have a link to a contrib module here :)

Moving to the provision_tasks_extra queue as per @cweagans in #12.

I doubt there would be much need for an addition to hosting_tasks_extra, or would anyone like to do this from the frontend?

Implementing a queue would probably be the best way forward to schedule regular triggering of this.

This saved me again today ... I used this to fix some db privilege issues after a DNS name change, which messed up some grants.

Together with #2175595-1: Generate drush groups I was able to quickly reset all passwords on a server.

Here's a patch based on the gist .. only with minor cleanup.

* Is the filename OK?
* We could make the maintenance mode optional .. I temporarily disabled it to avoid errors during my recovery.

I see that I accidentally committed this in fd9a94eea65015780d98c34b00fab4b4cbabe9a8 "Fix hook_drush_load() check for http_basic_auth"

Code still seems ok, so lets leave it at that. We can always open a follow-up issue.