-
Notifications
You must be signed in to change notification settings - Fork 394
@executeInDrupalVm annotation not respected #1582
Comments
Is your VM booted?
It strikes me that should work. Have you tested the alias? It looks like BLT cannot ssh into the VM. Can you test a command like |
That's also weird. Have you tried clearing your drush caches? |
Trying this on a fresh install now. vagrant exec:
drush status:
blt doctor:
blt frontend:
|
What does |
These are the two methods that really decide whether the VM is used:
I wonder if |
vagrant status
|
Sounds like this is the issue:
I have a different alias for each site. I've set my default alias to the one that connects to |
So maybe that check is bad? I need some way to determine if your local machine is configured to use DVM. It's possible that a given project has DVM config created, but a developer would like to opt out and use something else. In this case, they can change |
Hmm, yeah that is a little tricky. My knee-jerk response is to say that a top-level config value may be a more straight forward approach, as in: dvm: true It would be easy to toggle this off for individual developers and wouldn't rely on comparing config values that don't necessarily have to match otherwise. The current approach requires the developer to change a config value anyway if they want to opt out - this seems to make the relationship more explicit. To simply its usage, one of the DVM commands could set this value in |
Another thought if you'd like to make this more automated, you could always compare the output of Here, the developer could have DVM set up locally and halt it if they'd like to opt out, but for this you would have to check if But really, all of this might not be worth the extra effort if all I really have to do is change an alias name, which really isn't that difficult to do. And I can confirm that this begins to work as expected once that comparison passes. |
My system information:
Operating system type: macOS
Operating system version: 10.12.5
BLT version: 8.x-dev
Output of blt doctor:
When I run this command:
And I expected that my frontend tasks would be run inside the virtual machine. Instead my output indicates the frontend targets are being run on the host machine:
The text was updated successfully, but these errors were encountered: