builder/amazon: Added and corrected some default values in the docs.

This commit is contained in:
Rickard von Essen 2016-09-16 13:57:41 +02:00
parent d310de8cf5
commit 8193075c7c
No known key found for this signature in database
GPG Key ID: E0C0327388876CBA
2 changed files with 9 additions and 7 deletions

View File

@ -107,11 +107,11 @@ each category, the available configuration keys are alphabetized.
`{{.Command}}`. This may be useful to set if you want to set environmental `{{.Command}}`. This may be useful to set if you want to set environmental
variables or perhaps run it with `sudo` or so on. This is a configuration variables or perhaps run it with `sudo` or so on. This is a configuration
template where the `.Command` variable is replaced with the command to template where the `.Command` variable is replaced with the command to
be run. be run. Defaults to "{{.Command}}".
- `copy_files` (array of strings) - Paths to files on the running EC2 instance - `copy_files` (array of strings) - Paths to files on the running EC2 instance
that will be copied into the chroot environment prior to provisioning. This that will be copied into the chroot environment prior to provisioning. Defaults
is useful, for example, to copy `/etc/resolv.conf` so that DNS lookups work. to `/etc/resolv.conf` so that DNS lookups work.
- `device_path` (string) - The path to the device where the root volume of the - `device_path` (string) - The path to the device where the root volume of the
source AMI will be attached. This defaults to "" (empty string), which source AMI will be attached. This defaults to "" (empty string), which
@ -139,7 +139,7 @@ each category, the available configuration keys are alphabetized.
- `mount_path` (string) - The path where the volume will be mounted. This is - `mount_path` (string) - The path where the volume will be mounted. This is
where the chroot environment will be. This defaults to where the chroot environment will be. This defaults to
`packer-amazon-chroot-volumes/{{.Device}}`. This is a configuration template `/mnt/packer-amazon-chroot-volumes/{{.Device}}`. This is a configuration template
where the `.Device` variable is replaced with the name of the device where where the `.Device` variable is replaced with the name of the device where
the volume is attached. the volume is attached.

View File

@ -239,7 +239,8 @@ builder.
- `x509_upload_path` (string) - The path on the remote machine where the X509 - `x509_upload_path` (string) - The path on the remote machine where the X509
certificate will be uploaded. This path must already exist and be writable. certificate will be uploaded. This path must already exist and be writable.
X509 certificates are uploaded after provisioning is run, so it is perfectly X509 certificates are uploaded after provisioning is run, so it is perfectly
okay to create this directory as part of the provisioning process. okay to create this directory as part of the provisioning process. Defaults to
`/tmp`.
- `windows_password_timeout` (string) - The timeout for waiting for a Windows - `windows_password_timeout` (string) - The timeout for waiting for a Windows
password for Windows instances. Defaults to 20 minutes. Example value: "10m" password for Windows instances. Defaults to 20 minutes. Example value: "10m"
@ -327,8 +328,9 @@ include those files (see the `--no-filter` option of ec2-bundle-vol).
### Bundle Upload Command ### Bundle Upload Command
The default value for `bundle_upload_command` is shown below. It is split across The default value for `bundle_upload_command` is shown below. It is split across
multiple lines for convenience of reading. The bundle upload command is multiple lines for convenience of reading. Access key and secret key are omitted
responsible for taking the bundled volume and uploading it to S3. if using instance profile. The bundle upload command is responsible for taking
the bundled volume and uploading it to S3.
``` {.text} ``` {.text}
sudo -i -n ec2-upload-bundle \ sudo -i -n ec2-upload-bundle \