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

changed wording from builder to provisoner

Browse Source
This commit is contained in:
Levi Blaney 2018-07-16 19:13:05 -04:00 committed by GitHub
parent a5493e4906
commit f5e17d1cad
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/source/docs/provisioners/ansible.html.md
View File

@ -130,9 +130,9 @@ Optional Parameters:
- `set_winrm_passwd` (boolean) - Set to `true` if you are running on AWS, Azure or - `set_winrm_passwd` (boolean) - Set to `true` if you are running on AWS, Azure or
Google Compute and would like to access the generated password that Packer uses to Google Compute and would like to access the generated password that Packer uses to
connect to the instance via WinRM. The password will be avaliable on the builder connect to the instance via WinRM. The password will be avaliable to the Ansible
through the environment variable `GENERATED_WINRM_PASSWORD`. You will also need to provisioner through the environment variable `GENERATED_WINRM_PASSWORD`. You will
set `ansible_password` in your ansible playbook, for example, also need to set `ansible_password` in your ansible playbook, for example,
`ansible_password: "{{ lookup('env','GENERATED_WINRM_PASSWORD') }}"` `ansible_password: "{{ lookup('env','GENERATED_WINRM_PASSWORD') }}"`
## Default Extra Variables ## Default Extra Variables