So, having got a beta release out with the --configure-only option restored - before making a final release, let's consider the goal to get the basic upgrade functionality (the drush equivalent of the core upgrade UI - or, if you prefer, the D8 equivalent of drush updb) into drush itself as a core command. The --configure-only option uses contrib functionality (configuration entities provided by migrate_plus), so would not be a candidate to be added to drush. Is there a mechanism for contrib modules to add functionality to drush commands they don't implement? If not, it may make more sense to submit migrate-upgrade without --configure-only to drush, and implement a distinct migrate-upgrade-configure command in contrib.

I'm off for the next few days, just wanted to get my thoughts out there for discussion...

Comments

mikeryan created an issue. See original summary.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Virtuoso Performance commented
Parent issue: » #2709537: Move Drush commands into Drush itself

See also the issue for moving the command into core drush at https://github.com/drush-ops/drush/issues/2140, as well as the issue on our side at #2709537: Move Drush commands into Drush itself.

heddn’s picture

heddn
Primary language English
Location Nicaragua
CreditAttribution: heddn at MTech, LLC, Acro Commerce commented
Status: Active » Closed (outdated)

This probably won't happen. Just cleaning it up.