website: fix markdown to display inline backslash correctly (#11313)

pull/11320/head
Koya IWAMURA 5 years ago committed by GitHub
parent b2f9d58c5a
commit 7ebc85564b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -78,7 +78,7 @@ provisioner "powershell" {
running on AWS, Azure, Google Compute, or OpenStack and would like to access
the autogenerated password that Packer uses to connect to the instance via
WinRM, you can use the `build` template engine to inject it using
`{{ build `Password`}}`. In HCL templates, you can do the same thing by
```{{ build `Password` }}```. In HCL templates, you can do the same thing by
accessing the `build` variables For example:
<Tabs>
@ -97,7 +97,7 @@ provisioner "powershell" {
```json
{
"type": "powershell",
"environment_vars": ["WINRMPASS={{ build `Password`}}"],
"environment_vars": ["WINRMPASS={{ build `Password` }}"],
"inline": ["Write-Host \"Automatically generated aws password is: $Env:WINRMPASS\""]
},
```
@ -136,7 +136,7 @@ provisioner "powershell" {
running on AWS, Azure, Google Compute, or OpenStack and would like to access
the autogenerated password that Packer uses to connect to the instance via
WinRM, you can use the `build` template engine to inject it using
`{{ build `Password`}}`. In HCL templates, you can do the same thing by
```{{ build `Password` }}```. In HCL templates, you can do the same thing by
accessing the `build` variables For example:
<Tabs>
@ -156,7 +156,7 @@ provisioner "powershell" {
{
"type": "powershell",
"elevated_user": "Administrator",
"elevated_password": "{{ build `Password`}}",
"elevated_password": "{{ build `Password` }}",
...
},
```

Loading…
Cancel
Save