Define new hook_deploy_NAME hook and add new route to run their implementations from the UI

Would this not make Drush a hard dependency of Drupal?

Maybe I am confused. I just searched api.drupal.org and didn't find any hook_deploy_NAME(&$sandbox) isn't this hook something that drush does? Meaning, without drush not only can we not run this hook but core has no deploy hook implementation at all. Which would mean that this issue is about putting a front end in core for a drush only api. I could be wrong though.

@frob - this issue wants to create a new hook in drupal and provide a UI run it. The new hook would be documented in an api file in drupal core and it would then be like hook_update_n() - a hook invented by drupal that you can optionally run via Drush.

Drupal core wont have any implementations of the hook because this hook is meant to be used by sites and not by core and contrib.

@moshe #2901418: Add hook_post_config_import_NAME after config import was about adding that hook to core --and that keeps getting marked as duplicate. This issue is only about being able to invoke the deploy hook from drush with a /deploy.php route in core. At least that is how I read it. I am not saying I couldn't be wrong. But the only way to run a deploy hook is from drush and the only docs I can find on deploy hooks are in drush docs.

RE #8: Yes this issue is just as much about adding the hook_deploy_NAME to core as the other issue was about adding the other hook to core.

It is absolutely equivalent. The only difference is how the hook is called and when the hook is invoked.
In the other issue we wanted to invoke them at the end of a config import (bad idea, speaking from experience).
In this issue we want to make a dedicated UI which displays all pending hooks and invokes them in a batch process. (much better idea base on experience with drush)

There is nothing here that would make drupal depend on drush more than it already does (ie only for users who need drush to work with drupal, not in a technical sense). Drush is the command line user interface to run the update hooks. And drush is the command line user interface to run deploy hooks. It just so happens that drush supports the deploy hook already now whereas drupal doesn't yet because this issue here is not fixed yet. So the fact that the documentation exists only in drush is just a consequence of it not having been added to drupal core in this issue.

I updated the IS to show that this is about taking that hook_deploy_NAME hook from drush and adding it to core --not just add a deploy.php file that runs implemented hook_deploy_NAME hooks.

Deploy hooks do not need to be run from their own front controller (ie /core/deploy.php) but instead they can be run from a normal route like the config import.

Also I don't think we will need anything special, just a table with the pending hooks and a button to run them all.

I find this confusing. So is hook_deploy_NAME() going to be added to Drupal core (as opposed to drush only)? And if so, does anyone know the issue where this is being addressed?

RE #16: This here is that issue :D

I think one of the reasons this has not gained any traction is that almost everyone uses drush anyway and Drupal core or contrib should not actually have any deploy hooks. Deploy hooks are meant for modules that are unique to a specific site as the point is to being able to rely on a particular configuration which is exported and committed along with the hook implementation.

But if you wish to have a UI for it in core then this is the issue. Alternatively it would also be relatively easy to create a contrib module for it.
Ultimately this is something that has to be decided by ... the framework managers, I guess?

This issue. It will be added when someone is motivated to make an MR and shepherd it through to completion. So far nobody has turned up to do that.

Minor changes for clarity