beckermj/vaguerent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixes #9142 Add more information about shell script extensions

Browse Source 
This commit updates the shell provisioner docs to be more descriptive
about the kinds of extensions you can use with Windows
This commit is contained in:
Brian Cain 2020-04-21 09:27:43 -07:00
parent 10332d7ec6
commit 29b8bb3596
No known key found for this signature in database
GPG Key ID: 9FC4639B2E4510A0
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/source/docs/provisioning/shell.html.md
View File

@ -200,8 +200,15 @@ end
If you are running a Batch or PowerShell script for Windows, make sure
that the external path has the proper extension (".bat" or ".ps1"), because
Windows uses this to determine what kind of file it is to execute. If you
exclude this extension, it likely will not work.
Windows uses this to determine what kind of file it is to execute. Additionally,
if you are running Vagrant on something like Cygwin or WSL where bash is
available, then you should be able to use an extension like ".sh".
```ruby
Vagrant.configure("2") do |config|
config.vm.provision "shell", path: "scripts/PowershellScript.ps1"
end
```
To run a script already available on the guest you can use an inline script to
invoke the remote script on the guest.