You don't need BLT on Acquia Cloud

Remove core BLT packages

1. Ensure your site is ready for the migration

   • Ensure your site is running the latest versions of all Composer packages. Especially, ensure you are using the latest release of BLT (currently 13.7.4).
   • Ensure your default.local.settings.php (in docroot/sites/default/settings) is up to date and mode 755.
   • Ensure your site is running normally in your local and cloud environments.

2. Replace BLT settings with Drupal Recommended Settings

   Remove the blt.settings.php include from your settings.php. You can replace this with the Drupal Recommended Settings plugin, which provides all of the same settings functionality as BLT, including (but not limited to):

   • Caching
   • Configuration management (including Config Split)
   • Continuous integration
   • Logging
   • Public and private filesystem management

   composer require acquia/drupal-recommended-settings:dev-develop

   Update default.local.settings.php and local.settings.php to use the Environment Detector provided by Drupal Recommended Settings instead of BLT:

   use Acquia\Drupal\RecommendedSettings\Helpers\EnvironmentDetector

3. Remove BLT files

   Remove the BLT directory in your repo root: rm -rf blt

   Note that this does not purge all traces of BLT from your codebase. You may find references to BLT in the following files:

   • .gitignore
   • composer.json (autoload and scripts sections)

   However, we recommend you ensure your site is stable before doing any final cleanup. 

4. Set up GrumPHP

   BLT validates any changed code when you commit changes to your project. Third-party tools such as GrumPHP can do the same thing with more features and flexibility than BLT. Run the following command and review suggested plugins for safety and trust them when prompted.

   composer require --dev phpro/grumphp php-parallel-lint/php-parallel-lint

   To mimic the existing BLT pre-commit validation, do not accept the offer to create a grumphp.yml file. Instead, use this one:

   grumphp:
       tasks: { composer: null, phplint: null, yamllint: null }

    

5. Remove BLT, add Drush

   composer remove acquia/blt
   composer require drush/drush

    

6. Replace BLT commands with Composer scripts

   Replace BLT commands such as setup and validate with Composer equivalents by adding the following to the composer.json scripts section:

   {
     "drupal:install": "drush si minimal --existing-config",
     "drupal:test": "phpunit",
     "drupal:validate": "grumphp run"
   }

   Now instead of running blt setup, blt validate, and blt test, you can run composer drupal:install, composer drupal:validate, and composer drupal:test, respectively.

   You may need to make changes to these scripts based on your site configuration and test structure. For instance, tests may be run using Behat instead of PHPUnit, or you may need to install Drupal and import config as separate steps:

   drush si <your profile>
   drush config:set system.site uuid <uuid>
   drush cim

   Instead of explicitly setting UUID, you could also use a Drush hook or the Config Sync without Site UUID module.

Remove BLT from Pipelines

1. Update acquia-pipelines.yaml

   1. Remove the BLT_DIR environment variable.
   2. Replace call to setup_env script with: mysql -u root -proot -e "CREATE DATABASE IF NOT EXISTS drupal"
   3. Replace call to validate script with: composer drupal:validate
   4. Replace call to setup-app with: composer drupal:install
   5. Replace call to tests with: composer drupal:test
   6. Replace artifact build step with the following:

   - mkdir /tmp/acli-push-artifact
   - acli push:artifact --dry-run --no-clone --no-commit
   - mv .git /tmp/acli-push-artifact/
   - shopt -s dotglob && rm -rf ./* && mv /tmp/acli-push-artifact/* ./

    

2. Verify changes

   Commit and push these changes to your repository. Verify that Pipelines builds, tests, and deploys your site as expected.

   If assets such as frontend libraries are present in your source repository but missing from the build artifact, make sure they are properly defined as scaffold or vendor files in composer.json:

   "docroot/themes/custom/{$name}": [

     "type:drupal-custom-theme"

   ],

   This is necessary since ACLI deploys artifacts slightly differently than BLT. Whereas BLT used a hardcoded list of files to forcibly git add (the so-called "deploy gitignore file"), ACLI dynamically determines these files by checking for scaffold and vendor files defined in composer.json.

Remove BLT from Code Studio

Remove/replace Cloud Hooks

rm -rf hooks

#!/bin/bash

set -ev

drush updb
drush config:set system.site uuid 7139fc96-2b92-48c5-8e8a-cb79472aa19f
drush cim
drush cr

set +v

ln -s ../common.sh hooks/common/post-code-deploy/common.sh
ln -s ../common.sh hooks/common/post-code-update/common.sh
ln -s ../common.sh hooks/common/post-db-copy/common.sh

Remove/replace other BLT integrations