We regularly use provision-deploy to overwrite an existing production site with a fresh copy from staging. Each time provision-deploy is used on an already existing site, a new database is created. The old database never gets dropped however, resulting in obsolete databases.

Attached patch adds additional clean-up to post provision-deploy to remove the old database if necessary.

Comments

anarcat’s picture

Pushed to 2.x for further testing. Please find a third party to test this patch, when it's RTBC we'll merge it in 1.x.

It otherwise looks sound, I just don't have much time to test it myself and it's a quite sensitive area...

crea’s picture

Subs

steven jones’s picture

Version: 6.x-1.1 » 6.x-2.x-dev
Status: Needs review » Fixed

2.x will be released soonish, so marking this as fixed as per #1.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit 17501a2 on 7.x-2.x, dev-ssl-ip-allocation-refactor, dev-1205458-move_sites_out_of_platforms, 7.x-3.x, dev-subdir-multiserver, 6.x-2.x-backports, dev-helmo-3.x by anarcat:
    #1204990 by mr.baileys: Drop old database when re-deploying a site