From 7ebc85564b079df546ce10a6ef883872308410ec Mon Sep 17 00:00:00 2001 From: Koya IWAMURA Date: Fri, 8 Oct 2021 23:48:58 +0900 Subject: [PATCH] website: fix markdown to display inline backslash correctly (#11313) --- website/content/docs/provisioners/powershell.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/docs/provisioners/powershell.mdx b/website/content/docs/provisioners/powershell.mdx index 7c881b6e7..ea211a6ca 100644 --- a/website/content/docs/provisioners/powershell.mdx +++ b/website/content/docs/provisioners/powershell.mdx @@ -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: @@ -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: @@ -156,7 +156,7 @@ provisioner "powershell" { { "type": "powershell", "elevated_user": "Administrator", - "elevated_password": "{{ build `Password`}}", + "elevated_password": "{{ build `Password` }}", ... }, ```