Skip to content
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

BLT compatibility #59

Closed
danshumaker opened this issue Mar 27, 2020 · 2 comments
Closed

BLT compatibility #59

danshumaker opened this issue Mar 27, 2020 · 2 comments

Comments

@danshumaker
Copy link

Feature request related to Acquia BLT usage
I would imagine many users of acquia_cli would also use acquia/blt. But it appears they are incompatible in terms of composer packages.

Hoped for solution
This feature request is to make them compatible via composer.

Describe alternatives you've considered
Currently we have to install acquia_cli in a different location ( or repo ) so as not to interfere with the current projects composer setup that frequently requires blt. We can continue down this route but that is in-convenient when testing in a CI environment. We could also try using the phar install methods to get around the issue.

Additional context
Current environments tested in are docksal and Gitlab and Acquia Cloud.

Steps to reproduce

mkdir new-repo-test
cd new-repo-test
composer install acquia/blt
composer install typhonius/acquia_cli

I also tried this in the reverse order:

cd new-repo-test
rm -rf *
composer install typhonius/acquia_cli
composer install acquia/blt

Neither of these work at the moment.

Attaching screenshot of error. (Annotated-command & consolidation/robo issue)
blt-acquia-cli-no-bueno

@typhonius
Copy link
Owner

The reason for this is that Acquia Cli uses the newer release of Robo (2.x) whereas BLT <= 11 uses an older version (1.x).

It might be possible to support both Robo 1.x and Robo 2.x in order to support an installation into a BLT repo, but I would need to investigate that further over the coming weeks.

For now, my recommendation would be to use the Phar method (as it can be installed globally and will self-update for you).

@typhonius
Copy link
Owner

I'm going to close this issue for now and will deal with a follow-up when I get a response from the BLT team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants