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

fixing wording for proxy usage 👌

This commit is contained in:
John Davies-Colley 2017-12-06 17:13:02 +13:00
parent 92d1bdbdab
commit 76ac755ed9
4 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/source/docs/builders/amazon-ebs.html.md
View File

@ -338,8 +338,9 @@ builder.
otherwise the private IP address will be used. If not in a VPC the public DNS name
will be used.
If packer is configured for an outbound proxy. To configure WinRM traffic to bypass the proxy
`ssh_interface` can be set to `private_dns`.
Where Packer is configured for an outbound proxy but WinRM traffic should be direct
`ssh_interface` must be set to `private_dns` and `<region>.compute.internal` included
in the `NO_PROXY` environment variable.
- `subnet_id` (string) - If using VPC, the ID of the subnet, such as
`subnet-12345def`, where Packer will launch the EC2 instance. This field is

5
website/source/docs/builders/amazon-ebssurrogate.html.md
View File

@ -331,8 +331,9 @@ builder.
otherwise the private IP address will be used. If not in a VPC the public DNS name
will be used.
If packer is configured for an outbound proxy. To configure WinRM traffic to bypass the proxy
`ssh_interface` can be set to `private_dns`.
Where Packer is configured for an outbound proxy but WinRM traffic should be direct
`ssh_interface` must be set to `private_dns` and `<region>.compute.internal` included
in the `NO_PROXY` environment variable.
- `subnet_id` (string) - If using VPC, the ID of the subnet, such as
`subnet-12345def`, where Packer will launch the EC2 instance. This field is

5
website/source/docs/builders/amazon-ebsvolume.html.md
View File

@ -235,8 +235,9 @@ builder.
otherwise the private IP address will be used. If not in a VPC the public DNS name
will be used.
If packer is configured for an outbound proxy. To configure WinRM traffic to bypass the proxy
`ssh_interface` can be set to `private_dns`.
Where Packer is configured for an outbound proxy but WinRM traffic should be direct
`ssh_interface` must be set to `private_dns` and `<region>.compute.internal` included
in the `NO_PROXY` environment variable.
- `subnet_id` (string) - If using VPC, the ID of the subnet, such as
`subnet-12345def`, where Packer will launch the EC2 instance. This field is

7
website/source/docs/builders/amazon-instance.html.md
View File

@ -329,7 +329,7 @@ builder.
in AWS with the source instance, set the `ssh_keypair_name` field to the name
of the key pair.
- `ssh_private_ip` (boolean) - *Deprecated* use `ssh_interface` instead. If `true`,
- `ssh_private_ip` (boolean) - *Deprecated* use `ssh_interface` instead. If `true`,
then SSH will always use the private IP if available. Also works for WinRM.
- `ssh_interface` (string) - One of `public_ip`, `private_ip`,
@ -339,8 +339,9 @@ builder.
otherwise the private IP address will be used. If not in a VPC the public DNS name
will be used.
If packer is configured for an outbound proxy. To configure WinRM traffic to bypass the proxy
`ssh_interface` can be set to `private_dns`.
Where Packer is configured for an outbound proxy but WinRM traffic should be direct
`ssh_interface` must be set to `private_dns` and `<region>.compute.internal` included
in the `NO_PROXY` environment variable.
- `subnet_id` (string) - If using VPC, the ID of the subnet, such as
`subnet-12345def`, where Packer will launch the EC2 instance. This field is