Add custom file name parameter to drush bam-backup [#2068685]

At the moment it is not possible to give a backup filename as a command line parameter when using drush bam-backup command.

Usecase:
I want to automate the process of updating the staging server from dev. This would include these steps:

drush sql-sync and rsync from dev server
git pull and drush bam-backup on staging server

It would be very convenient to put the git commit id and commit message to the backup filename so it would be easily identified afterwards.

Example:
---Add-views-module.mysql.gz

Solution:
Add a file name parameter to bam-backup command that would override the default naming scheme if defined.

Comments

Comment #1

jiv_e CreditAttribution: jiv_e commented 19 August 2013 at 07:48

Assigned:

Unassigned

» jiv_e

Comment #2

amanire CreditAttribution: amanire commented 28 August 2013 at 14:26

Hi jiv_e,
I had been using a custom drush script to concatenate the git commit branch and hash into filenames. I realized that this could and probably should be done with backup and migrate, with a few custom tokens, but the random profile IDs used by BAM were a bit of a disappointing setback. However, I discovered that I could just manually change them in the backup_migrate database tables. So once I set up the profile and destination, I can just use

drush bb db backup_dir gitstamp

or something to that effect.

Comment #3

amanire CreditAttribution: amanire commented 28 August 2013 at 14:35

Actually, I'm now realizing that the fact that Backup and Migrate stores the profile settings in custom tables is a real limitation with the profile approach, since I want local environments settings.php to be able to override the paths in the DB.