Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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:
- Update package usage info
- rebuild caches
- create symlinks
Basically most of drush_provision_drupal_post_provision_install()
Opinions?
Comments
Comment #1
ergonlogicCross-referencing #1108152: Break out drush make calls in a new platform install task, as it addresses a comparable install->verify workflow for platform creation.
Comment #2
helmo CreditAttribution: helmo commentedpostponing to 3.x
Comment #3
anarcat CreditAttribution: anarcat commentedwe shouldn't duplicate code, but we should fire similar hooks so that the right data is passed to the frontend, in my opinion.
Comment #4
helmo CreditAttribution: helmo commented#2178749: db_name not available after install/import/migrate - requires verify to run. removed the need for this.