Check requirements before running updatedb

[alexpott]

See #1427

[damiankloip]

Maybe this should be a validation callback instead, so it's run before we hit the actual command? Then drush_update_check_requirements can just be used directly or the validation command can call out to that as the code is now.

[alexpott]

Well then we have to go through the rigmarole of loading all the .install files in the validation

[weitzman]

I get that update.php does this, but updatebd doesnt have to do everything that update.php does. updatedb lacks tests and i'm loath to put more weight on it without tests.

[alexpott]

The problem is that drush will run updates when core would not.

[weitzman]

Right. Some other command could validate requirements and then careful folks would chain calls to that command and then updatedb. Just saying that updatedb doesn't have to do it all.

[weitzman]

Merged into 8.x and master in order to help media entity contrib project.

[marcoscano]

Thanks!

[mootari]

When is the next release due?

[gideoncresswell]

This still does not work on a Drupal 7 site. The update_7.inc file runs the update_check_requirements() function but doesn't check if that returns TRUE or FALSE. And it doesn't call any hook_requirements() at all - just system_requirements().

Issue #1427 was closed in favour of this ticket, but the bug is still present.