DT-595: When provisioning a new multisite, Acquia code hooks will always fail

[bkosborne]

Adding a new multisite involves the following:

• Add the site settings folder to dev repo and commit
• Deploy build artifact to host (Acquia)
• Acquia's post code deploy hooks run as deploy artifact is deployed, which check if config needs to be imported or db updates be run for each multisite
• Command fails when it reaches the new multisite, because the site hasn't yet been installed, so drush cache rebuild errors out indicating a DB table is missing
• Acquia reports task as failed

Any workaround for this? I think we need a way for BLT to understand that a site's may not be installed yet (database has no tables) and to skip it when running drupal:config:import?

[mikemadison13]

@lcatlett is this something on your radar of existing multi-site issues or is this a new one?

[lcatlett]

this was fixed in #3231 and #3166. You might also want to validate that Cloud Hooks have been refreshed via blt setup:cloud-hooks and that Drush has been updated to the latest release, as there have been a number changes to host detection and mapping the correct multisite path which might otherwise result in drush losing the site context on older versions of drush 9.

@bkosborne - After updating to blt 9.2.x and provisioning a new multisite per the docs
in https://blt.readthedocs.io/en/latest/multisite/#acquia-cloud-setup do you still have this issue?

[lcatlett]

In reviewing other issues, I noticed that @bkosborne actually reported this issue in #2814, which I fixed in #2997 but the revert in #3028 re-introduced it. The solution proposed (18aab15) enables the dynamic creation of databases on ODE environments as well as site installs through BLT so I'll open a PR

[bkosborne]

Hi - Sorry for the delay. I have this on my list to test and provide more feedback, just haven't found the time yet.

[bkosborne]

@lcatlett The commit you linked to (18aab15) should indeed fix the original issue I reported (#2814), but I don't know how it would fix this particular issue. The problem I reported here is that drush cr command fails when it reaches a multisite that has not yet been installed and thus it's database (which already exists) doesn't have any tables in it. Drush craps out.

[richardbporter]

I would love to see a fix for this and would be willing to help. Is there a clear direction the maintainers want to go?

[richardbporter]

One potential workaround for this would be to:

• Explicitly define multisites in BLT configuration
• Deploy the new site code
• Install the site in the environment(s)
• Add the multisite to the BLT configuration

I think Cloud Hooks would work after that but it is an extra step that is a bit annoying. Its nice to have BLT dynamically get the list of multisites.

https://docs.acquia.com/blt/tech-architect/multisite/#add-a-multisite-array