Removing BLT on Acquia Cloud: How to Get Started

BLT provided two different types of hooks for your repository: one for Acquia Site Factory and another for Acquia Cloud Classic. I have added a couple of examples for each one of these.

If you are on Acquia Cloud Classic you should be moving soon to Acquia Cloud Next, which is recommended and you should use Acquia Cloud Actions to execute the tasks that before were done by the post-deploy-code hook. The examples here are primarily for Acquia Cloud Classic.

Post Deploy code for Acquia Site Factory

BLT replaced the post-site-install and the db-update Factory Hooks to run the drupal:update task, I have some example scripts here.

Note: This scripts are an example and should be tested before going into production.

This is just an example, use the one from the repo for the latest fixes.

#!/bin/bash
#
# Factory Hook: db-update
#
# This is an example script to perform necessary tasks using Drush
# commands during a database update on ACSF.
# Note: This is a starting point and may need customization.
#
# Usage: db-update.sh sitegroup env db-role domain custom-arg

# Exit immediately on error and enable verbose log output.
set -ev

# Map the script inputs to convenient names:
sitegroup="$1"
env="$2"
db_role="$3"
domain="$4"

# Get the internal domain name based on the site, environment, and db role arguments
uri=$(/usr/bin/env php /mnt/www/html/$sitegroup.$env/hooks/acquia/uri.php $sitegroup $env $db_role)
IFS='.' read -a name <<< "$uri"

# Drush executable
drush="/mnt/www/html/$sitegroup.$env/vendor/bin/drush"

echo "Running Drush deploy tasks on $uri domain in $env environment on the $sitegroup subscription."

# Execute the updates using Drush.
$drush --uri=$domain/ updatedb -y
result=$?
[ $result -ne 0 ] && exit $result

$drush --uri=$domain/ config-import -y
result=$?
[ $result -ne 0 ] && exit $result

$drush --uri=$domain/ config-import -y
result=$?
[ $result -ne 0 ] && exit $result

# Check config status
config_status_output=$($drush --uri=$domain/ config-status 2>&1)
if [[ "$config_status_output" != *"No differences"* ]]; then
  echo "Error: Config status check failed for site: $domain"
  echo "Details: $config_status_output"
  exit 1
fi

$drush --uri=$domain/ cache-rebuild
result=$?
[ $result -ne 0 ] && exit $result

$drush --uri=$domain/ deploy:hook -y
result=$?
[ $result -ne 0 ] && exit $result

# Clean up the Drush cache directory
echo "Removing temporary Drush cache files."
# Add any necessary cleanup commands here, for example:
# rm -rf /tmp/drush*

set +v

# Exit with the status of the last Drush command
exit $result

Post code deploy hook for Acquia Cloud Classic

BLT creates a post deploy code to ensure that Drush commands are run after new code is deployed. Remember, If you move into Acquia Cloud Next, this is done via Acquia Cloud Actions.

I have created and example here, test this code to see if it works for you. There are two examples:

• One script to run everything
• A more modular approach 

Here is the example of a monolithic hook:

#!/bin/bash

# Set the root directory relative to the script location
HOOKS_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
DRUPAL_ROOT="$(dirname "$(dirname "$HOOKS_DIR")")/docroot"

# Check if DRUPAL_ROOT exists and is a directory
if [ ! -d "$DRUPAL_ROOT" ]; then
  echo "Error: DRUPAL_ROOT directory does not exist: $DRUPAL_ROOT"
  exit 1
fi

# Set the path to the Drush command
DRUSH_CMD="$(dirname "$(dirname "$HOOKS_DIR")")/vendor/bin/drush"

# Check if the Drush command exists and is executable
if [ ! -x "$DRUSH_CMD" ]; then
  echo "Error: Drush command not found or not executable: $DRUSH_CMD"
  exit 1
fi

# Function to run Drush command for a given multisite
run_drush_for_multisite() {
  local site_path=$1
  local command=$2
  echo "Running Drush command for site: $site_path: $command"
  result=$($DRUSH_CMD --root="$DRUPAL_ROOT" --uri="$site_path" "$command" -y 2>&1)
  echo "$result"  # Debug statement to see the output
  # Check if the Drush command succeeded
  if [ $? -ne 0 ]; then
    echo "Error: Drush command '$command' failed for site: $site_path"
    exit 1
  fi

  # Special handling for config-status
  if [ "$command" == "config-status" ]; then
    if ! printf "%s" "$result" | grep -q "No differences"; then
      echo "Error: Config status check failed for site: $site_path"
      echo "Details: $result"
      exit 1
    fi
  fi
}

# Detect multisites by looking for settings.php files
MULTISITE_URIS=()

# Always ensure 'default' site is included
if [ -f "$DRUPAL_ROOT/sites/default/settings.php" ]; then
  MULTISITE_URIS+=("default")
else
  echo "Error: Default site settings.php not found in $DRUPAL_ROOT/sites/default"
  exit 1
fi

for site_path in "$DRUPAL_ROOT/sites"/*/; do
  if [ -f "${site_path}settings.php" ]; then
    site_uri=$(basename "$site_path")
    # Exclude 'default' as it's already added
    if [ "$site_uri" != "default" ]; then
      MULTISITE_URIS+=("$site_uri")
    fi
  fi
done

# Define the Drush commands to be executed for each multisite
DRUSH_COMMANDS=(
  "updatedb"
  "config-import"
  "config-import"
  "config-import"
  "config-status"
  "cache-rebuild"
  "deploy:hook"
)

# Run the Drush commands for each detected multisite
for site in "${MULTISITE_URIS[@]}"; do
  for command in "${DRUSH_COMMANDS[@]}"; do
    run_drush_for_multisite "$site" "$command"
  done
done

echo "Drush commands completed for all sites."