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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lost of Rollback database #37

Open
WengerK opened this issue Apr 16, 2021 · 0 comments
Open

Lost of Rollback database #37

WengerK opened this issue Apr 16, 2021 · 0 comments

Comments

@WengerK
Copy link
Member

WengerK commented Apr 16, 2021

馃挰 Is your feature request related to a problem? Please describe.

When using the automatic rollback feature, the system will:

  1. Backup the database before anything
after :updated, "drupal:db:backup"
  1. When something went wrong will run the rollback process (delete database and re-mount the previous dump
before :failed, "drupal:db:rollback"
  1. then cleanup old database backup
  before :cleanup, "drupal:db:backup:cleanup"

During the drupal:db:rollback we have to (optionally) save the used database into a specific location, to prevent drupal:db:backup:cleanup to remove very important dump (before deploy crash it was the initial database state).

馃 Describe the solution you'd like

Add a new configuration

set :keep_rollbacks, true

When use:

  • Copy the dump into a new directory rollback before any command

We also may add a new task drupal:db:rollback:check that ensure the rollback dir exists

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