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

Fixed documentation error for the 'source_machine_firewall_enabled' 

option.
This commit is contained in:
Jasper Siepkes 2016-12-31 12:34:33 +01:00
parent 7a90039b07
commit bdf57c9cfa
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/source/docs/builders/triton.html.md
View File

@ -84,10 +84,11 @@ builder.
- `source_machine_firewall_enabled` (boolean) - Whether or not the firewall of - `source_machine_firewall_enabled` (boolean) - Whether or not the firewall of
the VM used to create an image of is enabled. The Triton firewall only the VM used to create an image of is enabled. The Triton firewall only
filters inbound traffic to the VM. For the Joyent public cloud and private filters inbound traffic to the VM. All outbound traffic is always allowed.
Triton installations SSH traffic is always allowed by default. All outbound Currently this builder does not provide an interface to add specific
traffic is always allowed. Currently this builder does not provide an firewall rules. Unless you have a global rule defined in Triton which allows
interface to add specific firewall rules. The default is `false`. SSH traffic enabling the firewall will interfere with the SSH provisioner.
The default is `false`.
- `source_machine_metadata` (object of key/value strings) - Triton metadata - `source_machine_metadata` (object of key/value strings) - Triton metadata
applied to the VM used to create the image. Metadata can be used to pass applied to the VM used to create the image. Metadata can be used to pass
configuration information to the VM without the need for networking. See configuration information to the VM without the need for networking. See