Vagrant Powershell CLI does now allow additional arguments

[jackdneilson]

Debug output

vagrant powershell -- -ConfigurationName test
==> default: Detecting if a remote PowerShell connection can be made with the guest...
    default: Creating powershell session to 127.0.0.1:55985
    default: Username: vagrant
Cannot process command because a command is already specified with -Command or -EncodedCommand.

Expected behavior

Running vagrant powershell with additional parameters should process the additional parameters correctly, in this case attempting to use the session configuration "test".

Actual behavior

Regardless of what additional parameters are given, the error shown in debug output is printed.

Reproduction information

Attempt to run vagrant powershell with additional parameters using the -- syntax.

Vagrant version

Vagrant 2.4.9

Host operating system

Windows 10 22H2

Guest operating system

Windows 10 22H2

Steps to reproduce

1. Attempt to run vagrant powershell with additional parameters using the -- syntax.
2. The process fails with an error.

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "gusztavvargadr/windows-10"
  config.vm.box_version = "2506.0.0"
  config.vm.guest = :windows
  config.vm.communicator = "winrm"
end

[taru-garg-hashicorp]

Hi @jackdneilson,

I wonder if https://developer.hashicorp.com/vagrant/docs/cli/powershell is what you are looking for. I have very little experience with Powershell, but if you want to run a command on the Guest's powershell you can do something like
vagrant powershell -c COMMAND

Cheers!

[jackdneilson]

Hi @taru-garg-hashicorp,

My mistake - I saw in the source code that there was potential support for passing additional parameters but looking at the doc and vagrant powershell --help I can see I was mistaken.

The intention is not to run a single command, but to start a new interaction remote powershell session with additional arguments (in this case, loading a new profile using -ConfigurationName).

This issue can be safely closed or converted to feature request, and I'll have to find some other way to get a powershell profile to load on remote connection.

Thank you!

EDIT: I've tried changing the default powershell session configuration (Set-PSSessionConfiguration -Name microsoft.powershell -StartupScript C:\profile.ps1) but this causes vagrant up to crash. Very simply, I'm trying to add in an alias or two and change directory upon a remote session being started (the Windows equivalent of creating a ~/.bash_profile). If there is any scope to add Windows support to the docs it would be welcome, as I have been struggling for this issue for a few days now.