mirror of https://github.com/hashicorp/packer
Adrien Delorme
7 years ago
parent
c54879717b
commit
aeb898d598
@ -1,26 +1,39 @@
|
||||
<!-- Code generated from the comments of the Config struct in builder/amazon/instance/builder.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
- `ami_block_device_mappings` (awscommon.BlockDevices) - AMI Mappings
|
||||
- `launch_block_device_mappings` (awscommon.BlockDevices) - Launch Mappings
|
||||
- `bundle_destination` (string) - The directory on the running instance where
|
||||
the bundled AMI will be saved prior to uploading. By default this is
|
||||
/tmp. This directory must exist and be writable.
|
||||
- `ami_block_device_mappings` (awscommon.BlockDevices) - Add one or more block device mappings to the AMI. These will be attached
|
||||
when booting a new instance from your AMI. To add a block device during
|
||||
the Packer build see `launch_block_device_mappings` below. Your options
|
||||
here may vary depending on the type of VM you use. See the
|
||||
[BlockDevices](#block-devices-configuration) documentation for fields.
|
||||
|
||||
- `bundle_prefix` (string) - The prefix for files created from bundling the
|
||||
root volume. By default this is image-{{timestamp}}. The timestamp
|
||||
variable should be used to make sure this is unique, otherwise it can
|
||||
collide with other created AMIs by Packer in your account.
|
||||
- `launch_block_device_mappings` (awscommon.BlockDevices) - Add one or more block devices before the Packer build starts. If you add
|
||||
instance store volumes or EBS volumes in addition to the root device
|
||||
volume, the created AMI will contain block device mapping information
|
||||
for those volumes. Amazon creates snapshots of the source instance's
|
||||
root volume and any other EBS volumes described here. When you launch an
|
||||
instance from this new AMI, the instance automatically launches with
|
||||
these additional volumes, and will restore them from snapshots taken
|
||||
from the source instance. See the
|
||||
[BlockDevices](#block-devices-configuration) documentation for fields.
|
||||
|
||||
- `bundle_upload_command` (string) - The command to use to upload the bundled
|
||||
volume. See the "custom bundle commands" section below for more
|
||||
information.
|
||||
- `bundle_destination` (string) - The directory on the running instance where the bundled AMI will be
|
||||
saved prior to uploading. By default this is /tmp. This directory must
|
||||
exist and be writable.
|
||||
|
||||
- `bundle_vol_command` (string) - The command to use to bundle the volume.
|
||||
See the "custom bundle commands" section below for more information.
|
||||
- `bundle_prefix` (string) - The prefix for files created from bundling the root volume. By default
|
||||
this is image-{{timestamp}}. The timestamp variable should be used to
|
||||
make sure this is unique, otherwise it can collide with other created
|
||||
AMIs by Packer in your account.
|
||||
|
||||
- `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.
|
||||
X509 certificates are uploaded after provisioning is run, so it is
|
||||
perfectly okay to create this directory as part of the provisioning
|
||||
process. Defaults to /tmp.
|
||||
- `bundle_upload_command` (string) - The command to use to upload the bundled volume. See the "custom bundle
|
||||
commands" section below for more information.
|
||||
|
||||
- `bundle_vol_command` (string) - The command to use to bundle the volume. See the "custom bundle
|
||||
commands" section below for more information.
|
||||
|
||||
- `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. X509
|
||||
certificates are uploaded after provisioning is run, so it is perfectly
|
||||
okay to create this directory as part of the provisioning process.
|
||||
Defaults to /tmp.
|
||||
|
||||
@ -1,18 +1,16 @@
|
||||
<!-- Code generated from the comments of the Config struct in builder/amazon/instance/builder.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
- `account_id` (string) - Your AWS account ID. This is required for bundling
|
||||
the AMI. This is not the same as the access key. You can find your
|
||||
account ID in the security credentials page of your AWS account.
|
||||
- `account_id` (string) - Your AWS account ID. This is required for bundling the AMI. This is not
|
||||
the same as the access key. You can find your account ID in the security
|
||||
credentials page of your AWS account.
|
||||
|
||||
- `s3_bucket` (string) - The name of the S3 bucket to upload the AMI. This
|
||||
bucket will be created if it doesn't exist.
|
||||
- `s3_bucket` (string) - The name of the S3 bucket to upload the AMI. This bucket will be created
|
||||
if it doesn't exist.
|
||||
|
||||
- `x509_cert_path` (string) - The local path to a valid X509 certificate for
|
||||
your AWS account. This is used for bundling the AMI. This X509 certificate
|
||||
must be registered with your account from the security credentials page in
|
||||
the AWS console.
|
||||
- `x509_cert_path` (string) - The local path to a valid X509 certificate for your AWS account. This is
|
||||
used for bundling the AMI. This X509 certificate must be registered with
|
||||
your account from the security credentials page in the AWS console.
|
||||
|
||||
- `x509_key_path` (string) - The local path to the private key for the X509
|
||||
certificate specified by x509_cert_path. This is used for bundling the
|
||||
AMI.
|
||||
- `x509_key_path` (string) - The local path to the private key for the X509 certificate specified by
|
||||
x509_cert_path. This is used for bundling the AMI.
|
||||
|
||||
@ -1,3 +1,3 @@
|
||||
<!-- Code generated from the comments of the Config struct in builder/amazon/instance/builder.go; DO NOT EDIT MANUALLY -->
|
||||
Config is the configuration that is chained through the steps and
|
||||
settable from the template.
|
||||
Config is the configuration that is chained through the steps and settable
|
||||
from the template.
|
||||
|
||||
Loading…
Reference in new issue