You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
💬 Is your feature request related to a problem? Please describe.
When using the automatic rollback feature, the system will:
Backup the database before anything
after :updated, "drupal:db:backup"
When something went wrong will run the rollback process (delete database and re-mount the previous dump
before :failed, "drupal:db:rollback"
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
The text was updated successfully, but these errors were encountered:
💬 Is your feature request related to a problem? Please describe.
When using the automatic rollback feature, the system will:
During the
drupal:db:rollback
we have to (optionally) save the used database into a specific location, to preventdrupal: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
When use:
rollback
before any commandWe also may add a new task
drupal:db:rollback:check
that ensure therollback
dir existsThe text was updated successfully, but these errors were encountered: