lcatlett/blt-drush-alias

Acquia Drush Alias Generator Plugin for Acquia BLT

Maintainers

Details

github.com/lcatlett/blt-drush-alias

Homepage

Source

Issues

Installs: 300 228

Dependents: 0

Suggesters: 0

Security: 0

Stars: 10

Watchers: 3

Forks: 8

Open Issues: 2

2.0.1 2022-04-08 22:37 UTC

Requires

MIT 9ef494ca3c6853381a4bebc1aa5670a156c3055b

  • Lindsey Catlett

acquiaDrushblt

This package is auto-updated.

Last update: 2024-10-10 17:47:15 UTC

README

This is an Acquia BLT plugin that dynamically generates Acquia drush aliases for both Acquia Cloud and Acquia Cloud Site Factory projects.

This plugin is community-created and community-supported. Acquia does not provide any direct support for this software or provide any warranty as to its stability.

Quickstart

To use this plugin on your existing BLT 10 project, require the plugin with Composer:

composer require lcatlett/blt-drush-alias

Generate your Acquia drush aliases by calling aliases, which is a custom BLT command provided by this plugin:

blt aliases

This command will prompt you for a Acquia Cloud API v2 token and secret key as well as your Acquia application ID.

Run blt aliases again to update your ACE or ACSF drush aliases.

Installation and usage

To create a new BLT project and generate your Acquia drush aliases, run the following commands, replacing mysite with your desired BLT project name.

composer create-project --no-interaction acquia/blt-project mysite
cd mysite
composer require lcatlett/blt-drush-alias
blt aliases --no-interaction

Generate your Acquia drush aliases by calling aliases, which is a custom BLT command provided by this plugin:

blt aliases

This command will prompt you for a Acquia Cloud API v2 token and secret key as well as your Acquia application ID.

Run blt aliases again to update your ACE or ACSF drush aliases.

Why do I need this plugin?

This command previously existed in BLT, but was removed in favor of generating drush aliases through the Acquia Developer Studio cli which downloads Drush aliases per the Acquia docs. These drush aliases are not compatible with ACSF or multisite, nor are they dynamically updated to use custom domains. Additionally, the default Acquia drush aliases use the globally installed drush9 package which is problematic for a number of reasons.