In #1853620: Add db_name to site summary we need a database field to be populated in the hostmaster database.

This is now done in the verify task, but that does not run on new sites.

We could duplicate the code to also hook into a new site installation, but wouldn't this be nicer?

I guess this would allow us to trim more actions from the install task that are duplicated.
Such as:

  1. Update package usage info
  2. rebuild caches
  3. create symlinks

Basically most of drush_provision_drupal_post_provision_install()

Opinions?

Comments

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

Cross-referencing #1108152: Break out drush make calls in a new platform install task, as it addresses a comparable install->verify workflow for platform creation.

helmo’s picture

helmo commented
Version: 6.x-2.x-dev » 7.x-3.x-dev

postponing to 3.x

anarcat’s picture

anarcat commented

we shouldn't duplicate code, but we should fire similar hooks so that the right data is passed to the frontend, in my opinion.

helmo’s picture

helmo commented
Issue summary: View changes
Status: Active » Closed (works as designed)

#2178749: db_name not available after install/import/migrate - requires verify to run. removed the need for this.