vagrant-service-manager
vagrant-service-manager copied to clipboard
`vagrant service-manager env --help` requires a running machine
$subject, which should not be the case. Help command execution path should be irrespective of the machine running status.
And the logs
$ vagrant service-manager env --help
A Vagrant environment or target machine is required to run this
command. Run `vagrant init` to create a new Vagrant environment. Or,
get an ID of a target machine from `vagrant global-status` to run
this command on. A final option is to change to a directory with a
Vagrantfile and to try again.
This might be current behavior for every command --help
option.
This might be current behavior for every command --help option.
Right. I remember we fixed this bug in past, somehow it crept in again.
We'll need the tests!
@navidshaikh This was only fixed for default help. That is
$ vagrant service-manager --help / -h
as we have gone with assumption that every plugin command need machine to be running.