You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user updates vagrant, then vagrant plugins will have incorrect dependencies and need to expunge.
Unfortunately, the command suggested does not have --local so users who have local vagrant plugins who try to use the suggested command will complain that it does not work.
Expected behavior
The output should include a --local parameter so that the command fixes things for everybody, not just those who stick to global plugins only
Actual behavior
The output does not include a --local parameter
Reproduction information
Vagrant version
All versions of vagrant ruby
Host operating system
All Operating systems
Guest operating system
All guests
Steps to reproduce
install a vagrant plugin with --local
update vagrant
try to vagrant up and recieve error message
try to use the recommended expunge command
local plugins are not expunged and user is unaware that --local is needed to fix the problem
Vagrantfile
# all vagrant files are affected, contents of vagrant file are irrelevant
The text was updated successfully, but these errors were encountered:
If a user updates vagrant, then vagrant plugins will have incorrect dependencies and need to expunge.
Unfortunately, the command suggested does not have
--local
so users who have local vagrant plugins who try to use the suggested command will complain that it does not work.Expected behavior
The output should include a
--local
parameter so that the command fixes things for everybody, not just those who stick to global plugins onlyActual behavior
The output does not include a
--local
parameterReproduction information
Vagrant version
All versions of vagrant ruby
Host operating system
All Operating systems
Guest operating system
All guests
Steps to reproduce
--local
vagrant up
and recieve error message--local
is needed to fix the problemVagrantfile
# all vagrant files are affected, contents of vagrant file are irrelevant
The text was updated successfully, but these errors were encountered: