Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Tool Proposal: ac-db #2

Open
jeffgeorge opened this issue Aug 16, 2017 · 0 comments
Open

New Tool Proposal: ac-db #2

jeffgeorge opened this issue Aug 16, 2017 · 0 comments

Comments

@jeffgeorge
Copy link
Member

jeffgeorge commented Aug 16, 2017

Acquia's Database Manipulation tools in Drush leave something to be desired.

To download a latest database copy, you have to do the following:

  1. drush @site.env ac-database-list to get the list of database names, and parse the result
  2. drush @site.env ac-database-instance-backup-list dbname to get a list of available backups, which you then have to iterate over to get the last one
  3. drush @site.env ac-database-instance-backup-download dbname backup-id to actually download said backup
  4. Then it's on you to load it

This is awful. While you can technically do this and it should technically be faster, it's clumsy and easier to just go do it through the UI.

However, if I could just run ac-db @site.env download, I'd actually use it.

So that's what I'd like. Oh. and with pv for progress bar of the download, assuming one doesn't come out of the box when downloading a dump via Drush.

Once we've got downloading, I could see extending it to support loading backups into a local environment, possibly with pre-processing, though I know that's available via an existing one-liner drush command.

Building this will help with future iteration on ac-update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant