iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #6820 from hashicorp/fix_6664 

add docs about default shell to execute_command call
This commit is contained in:
Megan Marsh 2018-10-10 10:26:02 -07:00 committed by GitHub
parent f331327f24 a564b6c62a
commit bae7f0a787
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/source/docs/provisioners/powershell.html.md
View File

@ -105,10 +105,15 @@ Optional parameters:
manually configured by setting the values for `remote_path` and manually configured by setting the values for `remote_path` and
`remote_env_var_path` respectively. `remote_env_var_path` respectively.
If you use the SSH communicator and have changed your default shell, you
may need to modify your `execute_command` to make sure that the command is
valid and properly escaped; the default assumes that you have not changed
the default shell away from cmd.
- `elevated_user` and `elevated_password` (string) - If specified, the - `elevated_user` and `elevated_password` (string) - If specified, the
PowerShell script will be run with elevated privileges using the given PowerShell script will be run with elevated privileges using the given
Windows user. If you are running a build on AWS, Azure or Google Compute and would like to run using Windows user. If you are running a build on AWS, Azure or Google Compute and would like to run using
the generated password that Packer uses to connect to the instance via the generated password that Packer uses to connect to the instance via
WinRM, you may do so by using the template variable {{.WinRMPassword}}. WinRM, you may do so by using the template variable {{.WinRMPassword}}.
For example: For example: