-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for generating ACSF site aliases #2961
Conversation
…econdary API calls or Drupal bootstrap.
…y to support multisite.
This has been tested on 5+ ACSF customers successfully with the largest customer having 192 sites. |
I'm getting a PHP fatal immediately after entering the application id. It looks like YamlMunge really lives in the Acquia\Blt\Robo\Common namespace and not in Acquia\Blt\Robo\Commands\Generate\YamlMunge.
|
Alias generation is working fine for both ACSF and ACE and when creating a new project the typhonius/acquia-php-sdk-v2 package is brought in on the dev-master branch. Forcing the acquia-php-sdk-v2 package to update from 1.0.2 when blt is updated on existing projects is proving more difficult. In the end I had to manually require the package: |
@ba66e77 do you recall how you were updating BLT when you ran into the |
The process I was using to test the update path was:
|
I think instead of just running composer install you may need to run |
I've confirmed that you can update BLT with the needed package dependencies by adding the
output:
It may be worth calling this out in the release notes to prevent similar update issues for users |
Fixes #2914 #2925
Changes proposed:
blt recipes:aliases:init:acquia