Tested and verified using "make website".
Fix up the vmware, vbox and qemu builder and communicator docs.
Sort more things in alphabetical order.
Use backtick delimiters for values.
Wrap long lines to 80 characters.
Show actual default value for boot_wait.
Copy vrdp_bind_address info from vbox iso to vbox ovf builder.
Show defaults for vmx_remove_ethernet_interfaces.
Show default port values for ssh in vbox ovf builder.
Remove executable bit on openstack builder doc.
Show default for skip_compaction in vmware vmx builder.
Add a bunch of missing periods.
Remove a few redundant commas.
I know we rejected this idea back in #4061, but we are closer to being at a point
where we can host a version of the website on master, and this will help push that through.
The existing documentation example looks intimidating as it includes:
* variable interpolation
* configuration of the chef provisioner
* and it misses the `config_template` file
In the issue comments, [simpler and complete example](https://github.com/hashicorp/packer/issues/3355#issuecomment-198134727) exists already and works out of the box.
This change adds the simpler and complete example, while leaving the more complicated example intact.
RFC952 restricts hostname not to use underline(_) and period(.), so
private cloud with legacy DNS system does not allow just to use
image_name for name of server.
Add instance_name config option for servers which packer creates to
make instance_name configurable. If instance_name is not specified,
by default it works like the past using image_name for instance_name.
In order to allow Packer to connect to Private Triton installations
we now expose `insecure_skip_tls_verify` which, if set to true, will
allow the user to make requests to Triton installations that use a
certificate not signed by a trusted root CA
I think we were overcomplicating things. The SDK provides the correct
credential chain by default, so let's use that. This patch does a quick
check for static credentials and uses those if found, then defaults to
the default credential provider chain.
This patch also removes the metadata timeout argument. Current versions
of the SDK have short timeouts by default, so I don't believe this is
needed.
