-
Notifications
You must be signed in to change notification settings - Fork 22
Vagrant plugin vagrant-triggers
not installed automatically
#1
Comments
Thanks for the suggestion @mihalski! It is true, it requires the plugin, nevertheless, it will try to resolve that requirement by itself. Nevertheless, I guess there is no harm in adding it to the documentation. |
Really? When I tried to run it without the plugin it exited after the warning:
I was timing to see if it would take 10 minutes :) Closer to 15-20 on my crappy internet :P |
Hmmm... it should. Maybe there is a bug in that logic. I will change the labels on this issue for now... |
Link to the code that should trigger the dependency question: Line 70 in fe28a6f
|
Issue confirmed this is a coding error on my end. |
vagrant-triggers
not resolved automatically
vagrant-triggers
not resolved automaticallyvagrant-triggers
not installed automatically
@mihalski This issue is fixed in the current master branch, thus a fix will be included in the next release. |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Hi,
Just thought it might be worth mentioning that the vagrant-triggers plugin is required, otherwise you get the error:
After installing vagrant you have to:
Regards,
Michal
The text was updated successfully, but these errors were encountered: