Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PowerShell direct support for Hyper-V #16

Open
ghost opened this issue Apr 21, 2021 · 0 comments
Open

PowerShell direct support for Hyper-V #16

ghost opened this issue Apr 21, 2021 · 0 comments

Comments

@ghost
Copy link

ghost commented Apr 21, 2021

This issue was originally opened by @Sarafian as hashicorp/packer#6359. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.


Microsoft released recently this concept where PowerShell can connect to a VM just by using the VMName without the necessity to use credentials nor the target OS having a full network stack configured. This is known as PowerShell Direct.

This could be very useful when working with Hyper-V network configuration as internal. For the current provisioner to work, somehow the network stack needs to be fully configured, then it's IP it needs to become know and then the packer client can provision.

With PowerShell direct this won't be necessary any longer.

There is a similar request for the vagrant provisioners. There a new type of provisioner is being discussed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants