vagrant/plugins/providers/hyperv/scripts/get_switches.ps1

# This will have a SwitchType property. As far as I know the values are:
#
#   0 - Private
#   1 - Internal
#
# Include the following modules
$Dir = Split-Path $script:MyInvocation.MyCommand.Path
. ([System.IO.Path]::Combine($Dir, "utils\write_messages.ps1"))

$Switches = @(Hyper-V\Get-VMSwitch `
    | Select-Object Name,SwitchType,NetAdapterInterfaceDescription,Id)
Write-Output-Message $(ConvertTo-JSON $Switches)
providers/hyperv: add script to read switches 2014-02-27 07:47:28 +00:00			`# This will have a SwitchType property. As far as I know the values are:`
			`#`
			`# 0 - Private`
			`# 1 - Internal`
			`#`
providrs/hyperv: ask for the vswitch to use 2014-02-27 16:08:02 +00:00			`# Include the following modules`
			`$Dir = Split-Path $script:MyInvocation.MyCommand.Path`
			`. ([System.IO.Path]::Combine($Dir, "utils\write_messages.ps1"))`

Ensure Hyper-V cmdlets are fully qualified + This disambuguates calls to the Hyper-V functions for the Hyper-V provider. The ambiguity of some commands - such as `Get-VM` - causes the Hyper-V provider to fail on systems where VMware PowerCLI is installed. This change ensures that all calls to Hyper-V specific cmdlets or functions are prepended by `Hyper-V\`. This ensures the correct cmdlet calls are being made. + Resolves #8862. 2017-08-08 17:00:29 +00:00			$Switches = @(Hyper-V\Get-VMSwitch `
Reference Hyper-V switch by ID instead of name Keep track of selected Hyper-V switch using the ID instead of name to prevent any encoding issues that may occur switching between PowerShell and Ruby. With the IDs staying consistent, the switch name can be fetched from the provided ID. Fixes #9679 #8794 #9451 2018-04-27 23:52:16 +00:00			`\| Select-Object Name,SwitchType,NetAdapterInterfaceDescription,Id)`
providrs/hyperv: ask for the vswitch to use 2014-02-27 16:08:02 +00:00			`Write-Output-Message $(ConvertTo-JSON $Switches)`