Drush migrate:rollback should skip disabled migrations

Created on 7 April 2022, over 2 years ago
Updated 8 February 2024, 10 months ago

Problem/Motivation

Some migrations may be disabled for a number of reasons. Drush command migrate:rollback should skip all disabled migrations before any further operations.

At this moment, migrate:rollback command does:
1) without --skip-progress-bar option: Tries to initialize the Symfony Console progress bar. It can fail, for example, if the source DB table doesn't exist.
2) with --skip-progress-bar option: Ends with the message: [error] Migration <name> is busy with another operation: Disabled

Both cases don't make sense and we should avoid any operation on disabled migrations.

Proposed resolution

Skip disabled migrations.

πŸ› Bug report
Status

Needs review

Version

6.0

Component

Code

Created by

πŸ‡¨πŸ‡ΏCzech Republic martin_klima

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

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024