patch a couple small bugs

This commit is contained in:
Jeff Escalante 2020-03-31 16:08:52 -04:00
parent 899c0fd8a9
commit 8d917b6f77
No known key found for this signature in database
GPG Key ID: 32D23C61AB5450DB
2 changed files with 26 additions and 20 deletions

View File

@ -3,25 +3,24 @@
# See https://www.netlify.com/docs/redirects/ for documentation. Please do not # See https://www.netlify.com/docs/redirects/ for documentation. Please do not
# modify or delete existing redirects without first verifying internally. # modify or delete existing redirects without first verifying internally.
/docs/installation.html /docs/install/index.html 301! /docs/installation.html /docs/install 301!
/docs/command-line/machine-readable.html /docs/commands/index.html 301! /docs/command-line/machine-readable.html /docs/commands 301!
/docs/command-line/introduction.html /docs/commands/index.html 301! /docs/command-line/introduction.html /docs/commands 301!
/docs/templates/introduction.html /docs/templates/index.html 301! /docs/templates/introduction.html /docs/templates 301!
/docs/builders/azure-setup.html /docs/builders/azure.html 301! /docs/builders/azure-setup.html /docs/builders/azure 301!
/docs/templates/veewee-to-packer.html /guides/veewee-to-packer.html 301! /docs/templates/veewee-to-packer.html /guides/veewee-to-packer 301!
/docs/extend/developing-plugins.html /docs/extending/plugins.html 301! /docs/extend/developing-plugins.html /docs/extending/plugins 301!
/docs/extending/developing-plugins.html /docs/extending/plugins.html 301! /docs/extending/developing-plugins.html /docs/extending/plugins 301!
/docs/extend/builder.html /docs/extending/custom-builders.html 301! /docs/extend/builder.html /docs/extending/custom-builders 301!
/docs/getting-started/setup.html /docs/getting-started/install.html 301! /docs/getting-started/setup.html /docs/getting-started/install 301!
/docs/other/community.html /community-tools.html 301! /docs/other/community.html /community-tools 301!
/downloads-community.html /community-tools.html 301! /downloads-community.html /community-tools 301!
/community /community.html 301! /community/index.html /community 301!
/community/index.html /community.html 301! /docs/other/environmental-variables.html /docs/other/environment-variables 301!
/docs/other/environmental-variables.html /docs/other/environment-variables.html 301! /docs/platforms.html /docs/builders 301!
/docs/platforms.html /docs/builders/index.html 301! /intro/platforms.html /docs/builders 301!
/intro/platforms.html /docs/builders/index.html 301! /docs/templates/configuration-templates.html /docs/templates/engine 301!
/docs/templates/configuration-templates.html /docs/templates/engine.html 301! /docs/machine-readable/* /docs/commands 301!
/docs/machine-readable/* /docs/commands/index.html 301!
/docs/command-line/* /docs/commands/:splat 200 /docs/command-line/* /docs/commands/:splat 200
/docs/extend/* /docs/extending/:splat 200 /docs/extend/* /docs/extending/:splat 200

View File

@ -90,7 +90,14 @@ Here is a full list of the available functions for reference.
- **SSHPublicKey** and **SSHPrivateKey**: The public and private key that Packer uses to connect to the instance. - **SSHPublicKey** and **SSHPrivateKey**: The public and private key that Packer uses to connect to the instance.
These are unique to the SSH communicator and are unset when using other communicators. These are unique to the SSH communicator and are unset when using other communicators.
**SSHPublicKey** and **SSHPrivateKey** can have escape sequences and special characters so their output should be single quoted to avoid surprises. For example: **SSHPublicKey** and **SSHPrivateKey** can have escape sequences and special characters so their output should be single quoted to avoid surprises. For example:
`` json { ... "provisioners": [ { "type": "shell", "inline": [ "echo '{{ build `SSHPrivateKey`}}' > /tmp/packer-session.pem" ] } ] } ``
```json
{ ... "provisioners": [{
"type": "shell",
"inline": [ "echo '{{ build `SSHPrivateKey`}}' > /tmp/packer-session.pem" ]
}]
}
```
For backwards compatability, `WinRMPassword` is also available through this For backwards compatability, `WinRMPassword` is also available through this
engine, though it is no different than using the more general `Password`. engine, though it is no different than using the more general `Password`.