Contrib.social

Allow passing schedule to run via Drush

Open on Drupal.org →
Created on 30 April 2023, about 1 year ago
Updated 1 September 2023, 10 months ago

Problem/Motivation

When running a backup via Drush it should be possible to select which schedule to run via an argument.

Proposed resolution

Add an option to the backup_migrate:schedule_backup Drush command to select which backup to run.

Remaining tasks

Add an option to the backup_migrate:schedule_backup Drush command to select which backup to run.

User interface changes

New Drush argument to select which backup is ran.

API changes

TBD

Data model changes

TBD

✨ Feature request
Status

Active

Version

5.1

Component

Miscellaneous

Created by

🇺🇸United States DamienMcKenna NH, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @DamienMcKenna
  • Comment 10 months ago →
    🇫🇷France fgm Paris, France

    Seconding this: AFAICS, there is currently no way to have 2 schedules (e.g. DB+public) and run them, except recreating them as quick backups on the CLI. When using the default choice, the chosen backup appears to always be the first enabled one, which means that (a) it will also run on cron (b) the other one(s) will /only/ run on cron.

    This probably encourages people to use the not-recommended "Entire site" backup.

    IMHO this command should both allow non-schedules "schedules" to be run manually, and (b) specify which one(s) to run on the CLI.

    Is there any design consideration voluntarily excluding this, or is it just lack of time for executing it ?

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024