-
Notifications
You must be signed in to change notification settings - Fork 396
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
Manual setup required for sync:refresh #1875
Comments
@grasmash I think there are still some issues to work out with
When I was dumping out the $annotation_data in executeInDrupalVm(), I kept getting true even after trying the edit in #1877 . To get
|
Developers on our project are also reporting that even with the above commit/patch, they are still getting the error. Following the steps described by @gabe-connolly (i.e. executing everything related to sync on the host machine rather than vm) solves it. |
Additional fix for issue acquia#1875
My system information:
Output of
blt doctor
:all green
When I run this command:
I get the following output:
And I expected this to happen:
Sync to complete without error
Basically, BLT is executing the sync command from within the VM, which generally doesn't have access to the host machine's private SSH keys, so the attempt to connect to the remote server (ACE) fails.
To work around this, I enabled SSH key forwarding on my host machine by adding this to ~/.ssh/config:
However, this isn't a very sustainable solution. Ideally
blt sync:refresh
would just work OOTB without any additional setup required. This could be achieved by simply running the command outside the VM. If manual setup is required, it should be documented.The text was updated successfully, but these errors were encountered: