Closed shouah closed 5 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/168005551
The labels on this github issue will be updated when the story is started.
Apologies for the lack of response on this issue, up until now. Your request is sound and is a use-case that we'd like to support. We opted for option 1.
- Update the plugin to explicitly prefix all PowerShell commands with the Hyper-V prefix to ensure ambiguous execution
The code fix should be applied and present in our most recent CLI release: 0.0.17
.
$ cf install-plugin -r CF-Community cfdev
...
$ cf dev version
CLI: 0.0.17
BUILD: 14 (b36c82e)
Many thanks for bringing this to our attention.
Summary: When running CFDEV on Windows 10 which has powershell modules for both Hyper-V and VMware PowerCLI installed, which has duplicated commands like Get-VM, then then CF CLI plugin invokes the wrong command and fails unexpectedly.
Expected behavior: The command "cf dev start -f ...tgz" invokes the correct PowerShell commands under the hood
Observed behavior:
Request: Either:
powershell.exe -Command "Hyper-V\Get-VM -Name cfdev*"
cf dev start -f ...tgz -psprefix "Hyper-V"