Ensuring Drush commands run properly using Drush 8.x via Acquia Cloud Hooks
Any time there are major new versions of software, some of the tooling surrounding the software requires tweaks before everything works like it used to, or as it's documented. Since Drupal 8 and Drush 8 are both relatively young, I expect some growing pains here and there.
One problem I ran into lately was quite a head-scratcher: On Acquia Cloud, I had a cloud hook set up that was supposed to do the following after code deployments:
# Build a Drush alias (e.g. [subscription].[environment]).
drush_alias=${site}'.'${target_env}
# Run database updates.
drush @${drush_alias} updb -y
# Import configuration from code.
drush @${drush_alias} cim vcsThis code (well, with fra -y instead of cim) works fine for some Drupal 7 sites I work on in Acquia Cloud, but it seems that database updates were detected but never run, and configuration changes were detected but never made... it took a little time to see what was happening, but I eventually figured it out.
The tl;dr fix?