update code based on master and update docs

This commit is contained in:
Richard Nienaber 2018-04-24 10:35:27 +01:00
parent e2e7953fe4
commit db65c99bf4
2 changed files with 4 additions and 4 deletions

View File

@ -113,7 +113,7 @@ func (s *StepCreateWindowsPassword) Run(_ context.Context, state multistep.State
}
state.Put("winrm_password", data.password)
commonhelper.SetSharedState("winrm_password", data.password)
commonhelper.SetSharedState("winrm_password", data.password, c.PackerConfig.PackerBuildName)
return multistep.ActionContinue
}

View File

@ -73,7 +73,7 @@ Optional parameters:
inject prior to the execute\_command. The format should be `key=value`.
Packer injects some environmental variables by default into the
environment, as well, which are covered in the section below.
If you are running on AWS or Azure and would like to access the generated
If you are running on AWS, Azure or Google Compute and would like to access the generated
password that Packer uses to connect to the instance via
WinRM, you can use the template variable `{{.WinRMPassword}}` to set this
as an environment variable. For example:
@ -101,8 +101,8 @@ Optional parameters:
- `elevated_user` and `elevated_password` (string) - If specified, the
PowerShell script will be run with elevated privileges using the given
Windows user. If you are running a build on AWS and would like to run using
the AWS-generated password that Packer uses to connect to the instance via,
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,
WinRM, you may do so by using the template variable {{.WinRMPassword}}.
For example: