revert prettier formatting on generated partials
This commit is contained in:
Jeff Escalante
parent
2999934326
commit
6798b73305
|
|
@ -23,3 +23,4 @@
|
|||
|
||||
- `security_token` (string) - STS access token, can be set through template or by exporting as
|
||||
environment variable such as `export SECURITY_TOKEN=value`.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the AlicloudAccessConfig struct in builder/alicloud/ecs/access_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Config of alicloud
|
||||
|
|
|
|||
|
|
@ -3,11 +3,14 @@
|
|||
- `disk_name` (string) - The value of disk name is blank by default. [2,
|
||||
128] English or Chinese characters, must begin with an
|
||||
uppercase/lowercase letter or Chinese character. Can contain numbers,
|
||||
., \_ and -. The disk name will appear on the console. It cannot
|
||||
., _ and -. The disk name will appear on the console. It cannot
|
||||
begin with `http://` or `https://`.
|
||||
|
||||
- `disk_category` (string) - Category of the system disk. Optional values
|
||||
are: - cloud - general cloud disk - cloud_efficiency - efficiency cloud disk - cloud_ssd - cloud SSD
|
||||
are:
|
||||
- cloud - general cloud disk
|
||||
- cloud_efficiency - efficiency cloud disk
|
||||
- cloud_ssd - cloud SSD
|
||||
|
||||
- `disk_size` (int) - Size of the system disk, measured in GiB. Value
|
||||
range: [20, 500]. The specified value must be equal to or greater
|
||||
|
|
@ -33,3 +36,4 @@
|
|||
data disk. Otherwise, Packer will keep the encryption setting to what
|
||||
it was in the source image. Please refer to Introduction of ECS disk encryption
|
||||
for more details.
|
||||
|
||||
|
|
@ -2,13 +2,15 @@
|
|||
|
||||
- `system_disk_mapping` (AlicloudDiskDevice) - Image disk mapping for system
|
||||
disk.
|
||||
|
||||
- `disk_category` (string) - Category of the system disk. Optional values
|
||||
are: - `cloud` - general cloud disk - `cloud_efficiency` - efficiency cloud disk - `cloud_ssd` - cloud SSD
|
||||
are:
|
||||
- `cloud` - general cloud disk
|
||||
- `cloud_efficiency` - efficiency cloud disk
|
||||
- `cloud_ssd` - cloud SSD
|
||||
|
||||
For phased-out instance types and non-I/O optimized instances, the
|
||||
default value is cloud. Otherwise, the default value is
|
||||
cloud_efficiency.
|
||||
cloud\_efficiency.
|
||||
|
||||
- `disk_description` (string) - The value of disk description is blank by
|
||||
default. \[2, 256\] characters. The disk description will appear on the
|
||||
|
|
@ -29,7 +31,6 @@
|
|||
|
||||
- `disk_category` (string) - Category of the data disk. Optional values
|
||||
are:
|
||||
|
||||
- `cloud` - general cloud disk
|
||||
- `cloud_efficiency` - efficiency cloud disk
|
||||
- `cloud_ssd` - cloud SSD
|
||||
|
|
@ -47,7 +48,7 @@
|
|||
console. It cannot begin with `http://` or `https://`.
|
||||
|
||||
- `disk_device` (string) - Device information of the related instance:
|
||||
such as `/dev/xvdb` It is null unless the Status is In_use.
|
||||
such as `/dev/xvdb` It is null unless the Status is In\_use.
|
||||
|
||||
- `disk_name` (string) - The value of disk name is blank by default. \[2,
|
||||
128\] English or Chinese characters, must begin with an
|
||||
|
|
@ -56,7 +57,6 @@
|
|||
begin with `http://` or `https://`.
|
||||
|
||||
- `disk_size` (number) - Size of the data disk, in GB, values range:
|
||||
|
||||
- `cloud` - 5 \~ 2000
|
||||
- `cloud_efficiency` - 20 \~ 2048
|
||||
- `cloud_ssd` - 20 \~ 2048
|
||||
|
|
@ -77,3 +77,4 @@
|
|||
data disk. Otherwise, Packer will keep the encryption setting to what
|
||||
it was in the source image. Please refer to Introduction of [ECS disk encryption](https://www.alibabacloud.com/help/doc-detail/59643.htm)
|
||||
for more details.
|
||||
|
||||
|
|
@ -17,7 +17,7 @@
|
|||
- `image_copy_names` ([]string) - The name of the destination image,
|
||||
[2, 128] English or Chinese characters. It must begin with an
|
||||
uppercase/lowercase letter or a Chinese character, and may contain numbers,
|
||||
\_ or -. It cannot begin with `http://` or `https://`.
|
||||
_ or -. It cannot begin with `http://` or `https://`.
|
||||
|
||||
- `image_encrypted` (boolean) - Whether or not to encrypt the target images, including those copied if image_copy_regions is specified. If this option
|
||||
is set to true, a temporary image will be created from the provisioned
|
||||
|
|
@ -55,3 +55,4 @@
|
|||
containing a `name` and a `value` field. In HCL2 mode the
|
||||
[`dynamic_block`](/docs/configuration/from-1.5/expressions#dynamic-blocks)
|
||||
will allow you to create those programatically.
|
||||
|
||||
|
|
@ -2,5 +2,6 @@
|
|||
|
||||
- `image_name` (string) - The name of the user-defined image, [2, 128]
|
||||
English or Chinese characters. It must begin with an uppercase/lowercase
|
||||
letter or a Chinese character, and may contain numbers, \_ or -. It
|
||||
letter or a Chinese character, and may contain numbers, _ or -. It
|
||||
cannot begin with `http://` or `https://`.
|
||||
|
||||
|
|
@ -32,7 +32,7 @@
|
|||
- `security_group_name` (string) - The security group name. The default value
|
||||
is blank. [2, 128] English or Chinese characters, must begin with an
|
||||
uppercase/lowercase letter or Chinese character. Can contain numbers, .,
|
||||
\_ or -. It cannot begin with `http://` or `https://`.
|
||||
_ or -. It cannot begin with `http://` or `https://`.
|
||||
|
||||
- `user_data` (string) - User data to apply when launching the instance. Note
|
||||
that you need to be careful about escaping characters due to the templates
|
||||
|
|
@ -47,7 +47,7 @@
|
|||
|
||||
- `vpc_name` (string) - The VPC name. The default value is blank. [2, 128]
|
||||
English or Chinese characters, must begin with an uppercase/lowercase
|
||||
letter or Chinese character. Can contain numbers, \_ and -. The disk
|
||||
letter or Chinese character. Can contain numbers, _ and -. The disk
|
||||
description will appear on the console. Cannot begin with `http://` or
|
||||
`https://`.
|
||||
|
||||
|
|
@ -67,7 +67,6 @@
|
|||
|
||||
- `internet_charge_type` (string) - Internet charge type, which can be
|
||||
`PayByTraffic` or `PayByBandwidth`. Optional values:
|
||||
|
||||
- `PayByBandwidth`
|
||||
- `PayByTraffic`
|
||||
|
||||
|
|
@ -79,7 +78,6 @@
|
|||
public network, measured in Mbps (Mega bits per second).
|
||||
|
||||
Value range:
|
||||
|
||||
- `PayByBandwidth`: \[0, 100\]. If this parameter is not specified, API
|
||||
automatically sets it to 0 Mbps.
|
||||
- `PayByTraffic`: \[1, 100\]. If this parameter is not specified, an
|
||||
|
|
@ -93,3 +91,4 @@
|
|||
- `ssh_private_ip` (bool) - If this value is true, packer will connect to
|
||||
the ECS created through private ip instead of allocating a public ip or an
|
||||
EIP. The default value is false.
|
||||
|
||||
|
|
@ -9,3 +9,4 @@
|
|||
|
||||
- `source_image` (string) - This is the base image id which you want to
|
||||
create your customized images.
|
||||
|
||||
|
|
@ -97,11 +97,11 @@
|
|||
```
|
||||
|
||||
This selects the most recent Ubuntu 16.04 HVM EBS AMI from Canonical. NOTE:
|
||||
This will fail unless _exactly_ one AMI is returned. In the above example,
|
||||
This will fail unless *exactly* one AMI is returned. In the above example,
|
||||
`most_recent` will cause this to succeed by selecting the newest image.
|
||||
|
||||
- `filters` (map of strings) - filters used to select a `source_ami`.
|
||||
NOTE: This will fail unless _exactly_ one AMI is returned. Any filter
|
||||
NOTE: This will fail unless *exactly* one AMI is returned. Any filter
|
||||
described in the docs for
|
||||
[DescribeImages](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeImages.html)
|
||||
is valid.
|
||||
|
|
@ -121,7 +121,7 @@
|
|||
criteria provided in `source_ami_filter`; this pins the AMI returned by the
|
||||
filter, but will cause Packer to fail if the `source_ami` does not exist.
|
||||
|
||||
- `root_volume_tags` (map[string]string) - Tags to apply to the volumes that are _launched_. This is a [template
|
||||
- `root_volume_tags` (map[string]string) - Tags to apply to the volumes that are *launched*. This is a [template
|
||||
engine](/docs/templates/engine), see [Build template
|
||||
data](#build-template-data) for more information.
|
||||
|
||||
|
|
@ -132,3 +132,4 @@
|
|||
|
||||
- `ami_architecture` (string) - what architecture to use when registering the final AMI; valid options
|
||||
are "x86_64" or "arm64". Defaults to "x86_64".
|
||||
|
||||
|
|
@ -4,3 +4,4 @@
|
|||
currently running instance. This must be an EBS-backed AMI with a root
|
||||
volume snapshot that you have access to. Note: this is not used when
|
||||
from_scratch is set to true.
|
||||
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
<!-- Code generated from the comments of the Config struct in builder/amazon/chroot/builder.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Config is the configuration that is chained through the steps and settable
|
||||
from the template.
|
||||
|
|
|
|||
|
|
@ -71,7 +71,7 @@
|
|||
- `kms_key_id` (string) - ID, alias or ARN of the KMS key to use for boot volume encryption. This
|
||||
only applies to the main `region`, other regions where the AMI will be
|
||||
copied will be encrypted by the default EBS KMS key. For valid formats
|
||||
see _KmsKeyId_ in the [AWS API docs -
|
||||
see *KmsKeyId* in the [AWS API docs -
|
||||
CopyImage](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CopyImage.html).
|
||||
This field is validated by Packer, when using an alias, you will have to
|
||||
prefix `kms_key_id` with `alias/`.
|
||||
|
|
@ -81,9 +81,10 @@
|
|||
provided in `ami_regions`. If you just want to encrypt using a default
|
||||
ID, you can stick with `kms_key_id` and `ami_regions`. If you want a
|
||||
region to be encrypted with that region's default key ID, you can use an
|
||||
empty string `""` instead of a key id in this map. (e.g. `"us-east-1": ""`) However, you cannot use default key IDs if you are using this in
|
||||
empty string `""` instead of a key id in this map. (e.g. `"us-east-1":
|
||||
""`) However, you cannot use default key IDs if you are using this in
|
||||
conjunction with `snapshot_users` -- in that situation you must use
|
||||
custom keys. For valid formats see _KmsKeyId_ in the [AWS API docs -
|
||||
custom keys. For valid formats see *KmsKeyId* in the [AWS API docs -
|
||||
CopyImage](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CopyImage.html).
|
||||
|
||||
This option supercedes the `kms_key_id` option -- if you set both, and
|
||||
|
|
@ -116,3 +117,4 @@
|
|||
create volumes from the snapshot(s). By default no groups have permission
|
||||
to create volumes from the snapshot(s). all will make the snapshot
|
||||
publicly accessible.
|
||||
|
||||
|
|
@ -4,3 +4,4 @@
|
|||
AWS console or via APIs. This must be unique. To help make this unique,
|
||||
use a function like timestamp (see [template
|
||||
engine](/docs/templates/engine) for more info).
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the AMIConfig struct in builder/amazon/common/ami_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
AMIConfig is for common configuration related to creating AMIs.
|
||||
|
|
|
|||
|
|
@ -40,24 +40,23 @@
|
|||
generating credentials via the Vault engine, see the [Vault
|
||||
docs.](https://www.vaultproject.io/api/secret/aws#generate-credentials)
|
||||
If you set this flag, you must also set the below options:
|
||||
|
||||
- `name` (string) - Required. Specifies the name of the role to generate
|
||||
credentials against. This is part of the request URL.
|
||||
- `engine_name` (string) - The name of the aws secrets engine. In the
|
||||
Vault docs, this is normally referred to as "aws", and Packer will
|
||||
default to "aws" if `engine_name` is not set.
|
||||
- `role_arn` (string)- The ARN of the role to assume if credential_type
|
||||
on the Vault role is assumed_role. Must match one of the allowed role
|
||||
- `role_arn` (string)- The ARN of the role to assume if credential\_type
|
||||
on the Vault role is assumed\_role. Must match one of the allowed role
|
||||
ARNs in the Vault role. Optional if the Vault role only allows a single
|
||||
AWS role ARN; required otherwise.
|
||||
- `ttl` (string) - Specifies the TTL for the use of the STS token. This
|
||||
is specified as a string with a duration suffix. Valid only when
|
||||
credential_type is assumed_role or federation_token. When not
|
||||
specified, the default_sts_ttl set for the role will be used. If that
|
||||
credential\_type is assumed\_role or federation\_token. When not
|
||||
specified, the default\_sts\_ttl set for the role will be used. If that
|
||||
is also not set, then the default value of 3600s will be used. AWS
|
||||
places limits on the maximum TTL allowed. See the AWS documentation on
|
||||
the DurationSeconds parameter for AssumeRole (for assumed_role
|
||||
credential types) and GetFederationToken (for federation_token
|
||||
the DurationSeconds parameter for AssumeRole (for assumed\_role
|
||||
credential types) and GetFederationToken (for federation\_token
|
||||
credential types) for more details.
|
||||
|
||||
```json
|
||||
|
|
@ -69,3 +68,4 @@
|
|||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
|
@ -1,6 +1,7 @@
|
|||
<!-- Code generated from the comments of the AccessConfig struct in builder/amazon/common/access_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
- `access_key` (string) - The access key used to communicate with AWS. [Learn how to set this](/docs/builders/amazon#specifying-amazon-credentials). On EBS, this
|
||||
- `access_key` (string) - The access key used to communicate with AWS. [Learn how to set this]
|
||||
(/docs/builders/amazon#specifying-amazon-credentials). On EBS, this
|
||||
is not required if you are using `use_vault_aws_engine` for
|
||||
authentication instead.
|
||||
|
||||
|
|
@ -11,3 +12,4 @@
|
|||
- `secret_key` (string) - The secret key used to communicate with AWS. [Learn how to set
|
||||
this](/docs/builders/amazon#specifying-amazon-credentials). This is not required
|
||||
if you are using `use_vault_aws_engine` for authentication instead.
|
||||
|
||||
|
|
@ -40,3 +40,4 @@
|
|||
CopyImage](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CopyImage.html)
|
||||
This field is validated by Packer, when using an alias, you will have to
|
||||
prefix kms_key_id with alias/.
|
||||
|
||||
|
|
@ -1,5 +1,4 @@
|
|||
<!-- Code generated from the comments of the BlockDevice struct in builder/amazon/common/block_device.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
These will be attached when booting a new instance from your AMI. Your
|
||||
options here may vary depending on the type of VM you use.
|
||||
|
||||
|
|
@ -9,13 +8,11 @@ The following mapping will tell Packer to encrypt the root volume of the
|
|||
build instance at launch using a specific non-default kms key:
|
||||
|
||||
```json
|
||||
[
|
||||
{
|
||||
[{
|
||||
"device_name": "/dev/sda1",
|
||||
"encrypted": true,
|
||||
"kms_key_id": "1a2b3c4d-5e6f-1a2b-3c4d-5e6f1a2b3c4d"
|
||||
}
|
||||
]
|
||||
}]
|
||||
```
|
||||
|
||||
Documentation for Block Devices Mappings can be found here:
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@
|
|||
run. For Windows instances, it is sometimes desirable to [run
|
||||
Sysprep](http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ami-create-standard.html)
|
||||
which will stop the instance for you. If this is set to `true`, Packer
|
||||
_will not_ stop the instance but will assume that you will send the stop
|
||||
*will not* stop the instance but will assume that you will send the stop
|
||||
signal yourself through your final provisioner. You can do this with a
|
||||
[windows-shell
|
||||
provisioner](/docs/provisioners/windows-shell).
|
||||
|
|
@ -29,9 +29,7 @@
|
|||
```json
|
||||
{
|
||||
"type": "windows-shell",
|
||||
"inline": [
|
||||
"\"c:\\Program Files\\Amazon\\Ec2ConfigService\\ec2config.exe\" -sysprep"
|
||||
]
|
||||
"inline": ["\"c:\\Program Files\\Amazon\\Ec2ConfigService\\ec2config.exe\" -sysprep"]
|
||||
}
|
||||
```
|
||||
|
||||
|
|
@ -76,7 +74,9 @@
|
|||
"Version": "2012-10-17",
|
||||
"Statement": [
|
||||
{
|
||||
"Action": ["logs:*"],
|
||||
"Action": [
|
||||
"logs:*"
|
||||
],
|
||||
"Effect": "Allow",
|
||||
"Resource": "*"
|
||||
}
|
||||
|
|
@ -109,7 +109,7 @@
|
|||
|
||||
`security_group_ids` take precedence over this.
|
||||
|
||||
- `run_tags` (map[string]string) - Tags to apply to the instance that is that is _launched_ to create the
|
||||
- `run_tags` (map[string]string) - Tags to apply to the instance that is that is *launched* to create the
|
||||
EBS volumes. This is a [template engine](/docs/templates/engine),
|
||||
see [Build template data](#build-template-data) for more information.
|
||||
|
||||
|
|
@ -136,7 +136,7 @@
|
|||
"source_ami_filter": {
|
||||
"filters": {
|
||||
"virtualization-type": "hvm",
|
||||
"name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*",
|
||||
"name": "ubuntu/images/\*ubuntu-xenial-16.04-amd64-server-\*",
|
||||
"root-device-type": "ebs"
|
||||
},
|
||||
"owners": ["099720109477"],
|
||||
|
|
@ -146,11 +146,11 @@
|
|||
```
|
||||
|
||||
This selects the most recent Ubuntu 16.04 HVM EBS AMI from Canonical. NOTE:
|
||||
This will fail unless _exactly_ one AMI is returned. In the above example,
|
||||
This will fail unless *exactly* one AMI is returned. In the above example,
|
||||
`most_recent` will cause this to succeed by selecting the newest image.
|
||||
|
||||
- `filters` (map of strings) - filters used to select a `source_ami`.
|
||||
NOTE: This will fail unless _exactly_ one AMI is returned. Any filter
|
||||
NOTE: This will fail unless *exactly* one AMI is returned. Any filter
|
||||
described in the docs for
|
||||
[DescribeImages](http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeImages.html)
|
||||
is valid.
|
||||
|
|
@ -226,12 +226,12 @@
|
|||
```
|
||||
|
||||
This selects the Subnet with tag `Class` with the value `build`, which has
|
||||
the most free IP addresses. NOTE: This will fail unless _exactly_ one
|
||||
the most free IP addresses. NOTE: This will fail unless *exactly* one
|
||||
Subnet is returned. By using `most_free` or `random` one will be selected
|
||||
from those matching the filter.
|
||||
|
||||
- `filters` (map of strings) - filters used to select a `subnet_id`.
|
||||
NOTE: This will fail unless _exactly_ one Subnet is returned. Any
|
||||
NOTE: This will fail unless *exactly* one Subnet is returned. Any
|
||||
filter described in the docs for
|
||||
[DescribeSubnets](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeSubnets.html)
|
||||
is valid.
|
||||
|
|
@ -284,10 +284,10 @@
|
|||
|
||||
This selects the VPC with tag `Class` with the value `build`, which is not
|
||||
the default VPC, and have a IPv4 CIDR block of `/24`. NOTE: This will fail
|
||||
unless _exactly_ one VPC is returned.
|
||||
unless *exactly* one VPC is returned.
|
||||
|
||||
- `filters` (map of strings) - filters used to select a `vpc_id`. NOTE:
|
||||
This will fail unless _exactly_ one VPC is returned. Any filter
|
||||
This will fail unless *exactly* one VPC is returned. Any filter
|
||||
described in the docs for
|
||||
[DescribeVpcs](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeVpcs.html)
|
||||
is valid.
|
||||
|
|
@ -314,3 +314,4 @@
|
|||
should be direct, `ssh_interface` must be set to `private_dns` and
|
||||
`<region>.compute.internal` included in the `NO_PROXY` environment
|
||||
variable.
|
||||
|
||||
|
|
@ -7,3 +7,4 @@
|
|||
provisioned on the currently running instance. This must be an EBS-backed
|
||||
AMI with a root volume snapshot that you have access to. Note: this is not
|
||||
used when from_scratch is set to true.
|
||||
|
||||
|
|
@ -16,8 +16,8 @@
|
|||
from the source instance. See the
|
||||
[BlockDevices](#block-devices-configuration) documentation for fields.
|
||||
|
||||
- `run_volume_tags` (awscommon.TagMap) - Tags to apply to the volumes that are _launched_ to create the AMI.
|
||||
These tags are _not_ applied to the resulting AMI unless they're
|
||||
- `run_volume_tags` (awscommon.TagMap) - Tags to apply to the volumes that are *launched* to create the AMI.
|
||||
These tags are *not* applied to the resulting AMI unless they're
|
||||
duplicated in `tags`. This is a [template
|
||||
engine](/docs/templates/engine), see [Build template
|
||||
data](#build-template-data) for more information.
|
||||
|
|
@ -29,5 +29,6 @@
|
|||
For more information, see
|
||||
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/InstanceStorage.html.
|
||||
Because we don't validate the OS type of your guest, it is up to you to
|
||||
make sure you don't set this for \*nix guests; behavior may be
|
||||
make sure you don't set this for *nix guests; behavior may be
|
||||
unpredictable.
|
||||
|
||||
|
|
@ -5,3 +5,4 @@
|
|||
false, the block device will be mapped into the final created AMI. Set
|
||||
this option to true if you need a block device mounted in the surrogate
|
||||
AMI but not in the final created AMI.
|
||||
|
||||
|
|
@ -16,11 +16,12 @@
|
|||
from the source instance. See the
|
||||
[BlockDevices](#block-devices-configuration) documentation for fields.
|
||||
|
||||
- `run_volume_tags` (awscommon.TagMap) - Tags to apply to the volumes that are _launched_ to create the AMI.
|
||||
These tags are _not_ applied to the resulting AMI unless they're
|
||||
- `run_volume_tags` (awscommon.TagMap) - Tags to apply to the volumes that are *launched* to create the AMI.
|
||||
These tags are *not* applied to the resulting AMI unless they're
|
||||
duplicated in `tags`. This is a [template
|
||||
engine](/docs/templates/engine), see [Build template
|
||||
data](#build-template-data) for more information.
|
||||
|
||||
- `ami_architecture` (string) - what architecture to use when registering the
|
||||
final AMI; valid options are "x86_64" or "arm64". Defaults to "x86_64".
|
||||
|
||||
|
|
@ -7,3 +7,4 @@
|
|||
- `source_device_name` (string) - The device name of the block device on
|
||||
the source instance to be used as the root device for the AMI. This
|
||||
must correspond to a block device in `launch_block_device_mapping`.
|
||||
|
||||
|
|
@ -23,3 +23,4 @@
|
|||
|
||||
- `volume_size` (int64) - The size of the volume, in GiB. Required if
|
||||
not specifying a snapshot_id.
|
||||
|
||||
|
|
@ -8,3 +8,4 @@
|
|||
containing a `name` and a `value` field. In HCL2 mode the
|
||||
[`dynamic_block`](/docs/configuration/from-1.5/expressions#dynamic-blocks)
|
||||
will allow you to create those programatically.
|
||||
|
||||
|
|
@ -23,14 +23,14 @@
|
|||
source instance. See the [BlockDevices](#block-devices-configuration)
|
||||
documentation for fields.
|
||||
|
||||
- `run_volume_tags` (map[string]string) - Tags to apply to the volumes of the instance that is _launched_ to
|
||||
create EBS Volumes. These tags will _not_ appear in the tags of the
|
||||
- `run_volume_tags` (map[string]string) - Tags to apply to the volumes of the instance that is *launched* to
|
||||
create EBS Volumes. These tags will *not* appear in the tags of the
|
||||
resulting EBS volumes unless they're duplicated under `tags` in the
|
||||
`ebs_volumes` setting. This is a [template
|
||||
engine](/docs/templates/engine), see [Build template
|
||||
data](#build-template-data) for more information.
|
||||
|
||||
Note: The tags specified here will be _temporarily_ applied to volumes
|
||||
Note: The tags specified here will be *temporarily* applied to volumes
|
||||
specified in `ebs_volumes` - but only while the instance is being
|
||||
created. Packer will replace all tags on the volume with the tags
|
||||
configured in the `ebs_volumes` section as soon as the instance is
|
||||
|
|
@ -41,3 +41,4 @@
|
|||
the
|
||||
[`dynamic_block`](/docs/configuration/from-1.5/expressions#dynamic-blocks)
|
||||
will allow you to create those programatically.
|
||||
|
||||
|
|
@ -36,3 +36,4 @@
|
|||
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.
|
||||
|
||||
|
|
@ -13,3 +13,4 @@
|
|||
|
||||
- `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,4 +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.
|
||||
|
|
|
|||
|
|
@ -5,8 +5,8 @@
|
|||
- `capture_container_name` (string) - Capture Container Name
|
||||
- `shared_image_gallery` (SharedImageGallery) - Use a [Shared Gallery
|
||||
image](https://azure.microsoft.com/en-us/blog/announcing-the-public-preview-of-shared-image-gallery/)
|
||||
as the source for this build. _VHD targets are incompatible with this
|
||||
build type_ - the target must be a _Managed Image_.
|
||||
as the source for this build. *VHD targets are incompatible with this
|
||||
build type* - the target must be a *Managed Image*.
|
||||
|
||||
"shared_image_gallery": {
|
||||
"subscription": "00000000-0000-0000-0000-00000000000",
|
||||
|
|
@ -34,7 +34,8 @@
|
|||
|
||||
- `shared_image_gallery_timeout` (duration string | ex: "1h5m2s") - How long to wait for an image to be published to the shared image
|
||||
gallery before timing out. If your Packer build is failing on the
|
||||
Publishing to Shared Image Gallery step with the error `Original Error: context deadline exceeded`, but the image is present when you check your
|
||||
Publishing to Shared Image Gallery step with the error `Original Error:
|
||||
context deadline exceeded`, but the image is present when you check your
|
||||
Azure dashboard, then you probably need to increase this timeout from
|
||||
its default of "60m" (valid time units include `s` for seconds, `m` for
|
||||
minutes, and `h` for hours.)
|
||||
|
|
@ -161,7 +162,7 @@
|
|||
Not all Marketplace images support programmatic deployment, and support
|
||||
is controlled by the image publisher.
|
||||
|
||||
An example plan_info object is defined below.
|
||||
An example plan\_info object is defined below.
|
||||
|
||||
```json
|
||||
{
|
||||
|
|
@ -191,7 +192,8 @@
|
|||
- `polling_duration_timeout` (duration string | ex: "1h5m2s") - The default PollingDuration for azure is 15mins, this property will override
|
||||
that value. See [Azure DefaultPollingDuration](https://godoc.org/github.com/Azure/go-autorest/autorest#pkg-constants)
|
||||
If your Packer build is failing on the
|
||||
ARM deployment step with the error `Original Error: context deadline exceeded`, then you probably need to increase this timeout from
|
||||
ARM deployment step with the error `Original Error:
|
||||
context deadline exceeded`, then you probably need to increase this timeout from
|
||||
its default of "15m" (valid time units include `s` for seconds, `m` for
|
||||
minutes, and `h` for hours.)
|
||||
|
||||
|
|
@ -236,3 +238,4 @@
|
|||
temporary resource group asynchronously set this value. It's a boolean
|
||||
value and defaults to false. Important Setting this true means that
|
||||
your builds are faster, however any failed deletes are not reported.
|
||||
|
||||
|
|
@ -35,3 +35,4 @@
|
|||
`custom_managed_image_name` must also be set. See
|
||||
[documentation](https://docs.microsoft.com/en-us/azure/storage/storage-managed-disks-overview#images)
|
||||
to learn more about managed images.
|
||||
|
||||
|
|
@ -9,3 +9,4 @@
|
|||
across regions due to image synchronization latency. To ensure a consistent
|
||||
version across regions set this value to one that is available in all
|
||||
regions where you are deploying.
|
||||
|
||||
|
|
@ -47,3 +47,4 @@
|
|||
|
||||
- `image_hyperv_generation` (string) - The [Hyper-V generation type](https://docs.microsoft.com/en-us/rest/api/compute/images/createorupdate#hypervgenerationtypes).
|
||||
Defaults to `V1`.
|
||||
|
||||
|
|
@ -3,3 +3,4 @@
|
|||
- `source` (string) - Either a managed disk resource ID or a publisher:offer:sku:version specifier for plaform image sources.
|
||||
|
||||
- `image_resource_id` (string) - The image to create using this build.
|
||||
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
<!-- Code generated from the comments of the Config struct in builder/azure/chroot/builder.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Config is the configuration that is chained through the steps and settable
|
||||
from the template.
|
||||
|
|
|
|||
|
|
@ -23,3 +23,4 @@
|
|||
looked up using `subscription_id`.
|
||||
|
||||
- `subscription_id` (string) - The subscription to use.
|
||||
|
||||
|
|
@ -1,5 +1,4 @@
|
|||
<!-- Code generated from the comments of the Config struct in builder/azure/common/client/config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Config allows for various ways to authenticate Azure clients.
|
||||
When `client_id` and `subscription_id` are specified, Packer will use the
|
||||
specified Azure Active Directoty (AAD) Service Principal (SP).
|
||||
|
|
|
|||
|
|
@ -30,3 +30,4 @@
|
|||
|
||||
- `template_os` (string) - The name or ID of the template OS for the new
|
||||
template that will be created.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the Config struct in builder/cloudstack/config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Config holds all the details needed to configure the builder.
|
||||
|
|
|
|||
|
|
@ -26,7 +26,8 @@
|
|||
|
||||
- `snapshot_timeout` (duration string | ex: "1h5m2s") - How long to wait for an image to be published to the shared image
|
||||
gallery before timing out. If your Packer build is failing on the
|
||||
Publishing to Shared Image Gallery step with the error `Original Error: context deadline exceeded`, but the image is present when you check your
|
||||
Publishing to Shared Image Gallery step with the error `Original Error:
|
||||
context deadline exceeded`, but the image is present when you check your
|
||||
Azure dashboard, then you probably need to increase this timeout from
|
||||
its default of "60m" (valid time units include `s` for seconds, `m` for
|
||||
minutes, and `h` for hours.)
|
||||
|
|
@ -42,3 +43,4 @@
|
|||
data when launching the Droplet.
|
||||
|
||||
- `tags` ([]string) - Tags to apply to the droplet when it is created
|
||||
|
||||
|
|
@ -18,3 +18,4 @@
|
|||
image that will be used to launch a new droplet and provision it. See
|
||||
https://developers.digitalocean.com/documentation/v2/#list-all-images
|
||||
for details on how to get a list of the accepted image names/slugs.
|
||||
|
||||
|
|
@ -16,3 +16,4 @@
|
|||
- `aws_profile` (string) - The AWS shared credentials profile used to
|
||||
communicate with AWS. Learn how to set
|
||||
this.
|
||||
|
||||
|
|
@ -22,8 +22,10 @@
|
|||
used. This defaults to true if not set.
|
||||
|
||||
- `run_command` ([]string) - An array of arguments to pass to docker run in order to run the
|
||||
container. By default this is set to `["-d", "-i", "-t", "--entrypoint=/bin/sh", "--", "{{.Image}}"]` if you are using a linux
|
||||
container, and `["-d", "-i", "-t", "--entrypoint=powershell", "--", "{{.Image}}"]` if you are running a windows container. `{{.Image}}` is a
|
||||
container. By default this is set to `["-d", "-i", "-t",
|
||||
"--entrypoint=/bin/sh", "--", "{{.Image}}"]` if you are using a linux
|
||||
container, and `["-d", "-i", "-t", "--entrypoint=powershell", "--",
|
||||
"{{.Image}}"]` if you are running a windows container. `{{.Image}}` is a
|
||||
template variable that corresponds to the image template option. Passing
|
||||
the entrypoint option this way will make it the default entrypoint of
|
||||
the resulting image, so running docker run -it --rm will start the
|
||||
|
|
@ -57,3 +59,4 @@
|
|||
for the duration of the pull. If true login_server is required and
|
||||
login, login_username, and login_password will be ignored. For more
|
||||
information see the section on ECR.
|
||||
|
||||
|
|
@ -12,3 +12,4 @@
|
|||
will be pulled from the Docker registry if it doesn't already exist.
|
||||
|
||||
- `message` (string) - Set a message for the commit.
|
||||
|
||||
|
|
@ -31,9 +31,8 @@
|
|||
- `image_description` (string) - The description of the resulting image.
|
||||
|
||||
- `image_encryption_key` (\*CustomerEncryptionKey) - Image encryption key to apply to the created image. Possible values:
|
||||
|
||||
- kmsKeyName - The name of the encryption key that is stored in Google Cloud KMS.
|
||||
- RawKey: - A 256-bit customer-supplied encryption key, encodes in RFC 4648 base64.
|
||||
* kmsKeyName - The name of the encryption key that is stored in Google Cloud KMS.
|
||||
* RawKey: - A 256-bit customer-supplied encryption key, encodes in RFC 4648 base64.
|
||||
|
||||
example:
|
||||
|
||||
|
|
@ -83,7 +82,7 @@
|
|||
- `on_host_maintenance` (string) - Sets Host Maintenance Option. Valid choices are `MIGRATE` and
|
||||
`TERMINATE`. Please see [GCE Instance Scheduling
|
||||
Options](https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options),
|
||||
as not all machine_types support `MIGRATE` (i.e. machines with GPUs).
|
||||
as not all machine\_types support `MIGRATE` (i.e. machines with GPUs).
|
||||
If preemptible is true this can only be `TERMINATE`. If preemptible is
|
||||
false, it defaults to `MIGRATE`
|
||||
|
||||
|
|
@ -137,3 +136,4 @@
|
|||
instance. For more information, see the Vault docs:
|
||||
https://www.vaultproject.io/docs/commands/#environment-variables
|
||||
Example:`"vault_gcp_oauth_engine": "gcp/token/my-project-editor",`
|
||||
|
||||
|
|
@ -13,3 +13,4 @@
|
|||
|
||||
- `zone` (string) - The zone in which to launch the instance used to create the image.
|
||||
Example: "us-central1-a"
|
||||
|
||||
|
|
@ -1,5 +1,4 @@
|
|||
<!-- Code generated from the comments of the Config struct in builder/googlecompute/config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Config is the configuration structure for the GCE builder. It stores
|
||||
both the publicly settable state as well as the privately generated
|
||||
state of the config object.
|
||||
|
|
|
|||
|
|
@ -79,3 +79,4 @@
|
|||
- `user_data` (string) - User data to launch with the server. Packer will not
|
||||
automatically wait for a user script to finish before shutting down the
|
||||
instance, this must be handled in a provisioner.
|
||||
|
||||
|
|
@ -13,3 +13,4 @@
|
|||
- `vm_type` (string) - ID or name of the type this server should be created with.
|
||||
|
||||
- `disk_size` (float32) - Size of the created disk, in GiB.
|
||||
|
||||
|
|
@ -114,15 +114,14 @@
|
|||
treatment when choosing a boot device.
|
||||
|
||||
For Generation 1:
|
||||
|
||||
- `IDE`
|
||||
- `CD` _or_ `DVD`
|
||||
- `CD` *or* `DVD`
|
||||
- `Floppy`
|
||||
- `NET`
|
||||
|
||||
For Generation 2:
|
||||
|
||||
- `IDE:x:y`
|
||||
- `SCSI:x:y`
|
||||
- `CD` _or_ `DVD`
|
||||
- `CD` *or* `DVD`
|
||||
- `NET`
|
||||
|
||||
|
|
@ -7,3 +7,4 @@
|
|||
packer is executed from. This directory must not exist or, if
|
||||
created, must be empty prior to running the builder. By default this is
|
||||
"output-BUILDNAME" where "BUILDNAME" is the name of the build.
|
||||
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
<!-- Code generated from the comments of the Builder struct in builder/hyperv/iso/builder.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Builder implements packer.Builder and builds the actual Hyperv
|
||||
images.
|
||||
|
|
|
|||
|
|
@ -20,3 +20,4 @@
|
|||
disk_block_size will be ignored. The most likely use case for this
|
||||
option is outputing a disk that is in the format required for upload to
|
||||
Azure.
|
||||
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
<!-- Code generated from the comments of the Builder struct in builder/hyperv/vmcx/builder.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Builder implements packer.Builder and builds the actual Hyperv
|
||||
images.
|
||||
|
|
|
|||
|
|
@ -21,3 +21,4 @@
|
|||
- `copy_in_compare` (bool) - When cloning a vm to build from, we run a powershell
|
||||
Compare-VM command, which, depending on your version of Windows, may need
|
||||
the "Copy" flag to be set to true or false. Defaults to "false". Command:
|
||||
|
||||
|
|
@ -38,3 +38,4 @@
|
|||
- `target_runlevel` (int) - The minimum run level to wait for the
|
||||
container to reach. Note some distributions (Ubuntu) simulate run levels
|
||||
and may report 5 rather than 3.
|
||||
|
||||
|
|
@ -6,3 +6,4 @@
|
|||
|
||||
- `template_environment_vars` ([]string) - Environmental variables to
|
||||
use to build the template with.
|
||||
|
||||
|
|
@ -20,3 +20,4 @@
|
|||
|
||||
- `launch_config` (map[string]string) - List of key/value pairs you wish to
|
||||
pass to lxc launch via --config. Defaults to empty.
|
||||
|
||||
|
|
@ -3,3 +3,4 @@
|
|||
- `image` (string) - The source image to use when creating the build
|
||||
container. This can be a (local or remote) image (name or fingerprint).
|
||||
E.G. my-base-image, ubuntu-daily:x, 08fababf6f27, ...
|
||||
|
||||
|
|
@ -29,3 +29,4 @@
|
|||
winrm access when you create a Windows server. An ACG that specifies an
|
||||
access source (0.0.0.0/0) and allowed port (5985) must be created in
|
||||
advance.
|
||||
|
||||
|
|
@ -4,3 +4,4 @@
|
|||
(member_server_image_no is required if not specified)
|
||||
|
||||
- `server_product_code` (string) - Product (spec) code to create.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the Config struct in builder/ncloud/config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Config is structure to use packer builder plugin for Naver Cloud Platform
|
||||
|
|
|
|||
|
|
@ -52,3 +52,4 @@
|
|||
[documentation](https://docs.openstack.org/os-client-config/latest/user/configuration.html)
|
||||
for more information about `clouds.yaml` files. If omitted, the
|
||||
`OS_CLOUD` environment variable is used.
|
||||
|
||||
|
|
@ -13,3 +13,4 @@
|
|||
- `identity_endpoint` (string) - The URL to the OpenStack Identity service. If not specified, Packer will
|
||||
use the environment variables OS_AUTH_URL, if set. This is not required
|
||||
if using cloud.yaml.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the AccessConfig struct in builder/openstack/access_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
AccessConfig is for common configuration related to openstack access
|
||||
|
|
|
|||
|
|
@ -14,3 +14,4 @@
|
|||
- `image_tags` ([]string) - List of tags to add to the image after creation.
|
||||
|
||||
- `image_min_disk` (int) - Minimum disk size needed to boot image, in gigabytes.
|
||||
|
||||
|
|
@ -1,3 +1,4 @@
|
|||
<!-- Code generated from the comments of the ImageConfig struct in builder/openstack/image_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
- `image_name` (string) - The name of the resulting image.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the ImageConfig struct in builder/openstack/image_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
ImageConfig is for common configuration related to creating Images.
|
||||
|
|
|
|||
|
|
@ -6,3 +6,4 @@
|
|||
|
||||
- `most_recent` (bool) - Selects the newest created image when true. This is most useful for
|
||||
selecting a daily distro build.
|
||||
|
||||
|
|
@ -90,4 +90,5 @@
|
|||
|
||||
- `openstack_provider` (string) - Not really used, but here for BC
|
||||
|
||||
- `use_floating_ip` (bool) - _Deprecated_ use `floating_ip` or `floating_ip_pool` instead.
|
||||
- `use_floating_ip` (bool) - *Deprecated* use `floating_ip` or `floating_ip_pool` instead.
|
||||
|
||||
|
|
@ -28,14 +28,14 @@
|
|||
```
|
||||
|
||||
This selects the most recent production Ubuntu 16.04 shared to you by
|
||||
the given owner. NOTE: This will fail unless _exactly_ one image is
|
||||
the given owner. NOTE: This will fail unless *exactly* one image is
|
||||
returned, or `most_recent` is set to true. In the example of multiple
|
||||
returned images, `most_recent` will cause this to succeed by selecting
|
||||
the newest image of the returned images.
|
||||
|
||||
- `filters` (map of strings) - filters used to select a
|
||||
`source_image`.
|
||||
NOTE: This will fail unless _exactly_ one image is returned, or
|
||||
NOTE: This will fail unless *exactly* one image is returned, or
|
||||
`most_recent` is set to true. Of the filters described in
|
||||
[ImageService](https://developer.openstack.org/api-ref/image/v2/), the
|
||||
following are valid:
|
||||
|
|
@ -57,3 +57,4 @@
|
|||
|
||||
- `flavor` (string) - The ID, name, or full URL for the desired flavor for the server to be
|
||||
created.
|
||||
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
<!-- Code generated from the comments of the RunConfig struct in builder/openstack/run_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
RunConfig contains configuration for running an instance from a source image
|
||||
and details on how to access that launched image.
|
||||
|
|
|
|||
|
|
@ -11,3 +11,4 @@
|
|||
|
||||
- `usb` (bool) - Specifies whether to enable the USB bus when building
|
||||
the VM. Defaults to false.
|
||||
|
||||
|
|
@ -6,3 +6,4 @@
|
|||
is executed. This directory must not exist or be empty prior to running
|
||||
the builder. By default this is "output-BUILDNAME" where "BUILDNAME" is the
|
||||
name of the build.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the OutputConfig struct in builder/parallels/common/output_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
OutputConfig contains the configuration for builder's output.
|
||||
|
|
|
|||
|
|
@ -10,3 +10,4 @@
|
|||
template, where the Name
|
||||
variable is replaced with the VM name. More details on how to use prlctl
|
||||
are below.
|
||||
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
<!-- Code generated from the comments of the PrlctlConfig struct in builder/parallels/common/prlctl_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
PrlctlConfig contains the configuration for running "prlctl" commands
|
||||
before the VM start.
|
||||
|
|
|
|||
|
|
@ -3,3 +3,4 @@
|
|||
- `prlctl_post` ([][]string) - Identical to prlctl, except
|
||||
that it is run after the virtual machine is shutdown, and before the virtual
|
||||
machine is exported.
|
||||
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
<!-- Code generated from the comments of the PrlctlPostConfig struct in builder/parallels/common/prlctl_post_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
PrlctlPostConfig contains the configuration for running "prlctl" commands
|
||||
in the end of artifact build.
|
||||
|
|
|
|||
|
|
@ -5,3 +5,4 @@
|
|||
the machine. This information can be useful for provisioning. By default
|
||||
this is ".prlctl_version", which will generally upload it into the
|
||||
home directory.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the PrlctlVersionConfig struct in builder/parallels/common/prlctl_version_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
PrlctlVersionConfig contains the configuration for `prlctl` version.
|
||||
|
|
|
|||
|
|
@ -14,3 +14,4 @@
|
|||
be attached as a CD device to the virtual machine. If the mode is "upload"
|
||||
the Parallels Tools ISO will be uploaded to the path specified by
|
||||
parallels_tools_guest_path. The default value is "upload".
|
||||
|
||||
|
|
@ -4,3 +4,4 @@
|
|||
install into the VM. Valid values are "win", "lin", "mac", "os2"
|
||||
and "other". This can be omitted only if parallels_tools_mode
|
||||
is "disable".
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the ToolsConfig struct in builder/parallels/common/tools_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
ToolsConfig contains the builder configuration related to Parallels Tools.
|
||||
|
|
|
|||
|
|
@ -37,3 +37,4 @@
|
|||
- `vm_name` (string) - This is the name of the PVM directory for the new
|
||||
virtual machine, without the file extension. By default this is
|
||||
"packer-BUILDNAME", where "BUILDNAME" is the name of the build.
|
||||
|
||||
|
|
@ -13,3 +13,4 @@
|
|||
- `reassign_mac` (bool) - If this is "false" the MAC address of the first
|
||||
NIC will reused when imported else a new MAC address will be generated
|
||||
by Parallels. Defaults to "false".
|
||||
|
||||
|
|
@ -2,3 +2,4 @@
|
|||
|
||||
- `source_path` (string) - The path to a PVM directory that acts as the source
|
||||
of this build.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the Config struct in builder/parallels/pvm/config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
Config is the configuration structure for the builder.
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@
|
|||
^\* Please be aware that use of the `scsi` disk interface has been
|
||||
disabled by Red Hat due to a bug described
|
||||
[here](https://bugzilla.redhat.com/show_bug.cgi?id=1019220). If you are
|
||||
running Qemu on RHEL or a RHEL variant such as CentOS, you _must_ choose
|
||||
running Qemu on RHEL or a RHEL variant such as CentOS, you *must* choose
|
||||
one of the other listed interfaces. Using the `scsi` interface under
|
||||
these circumstances will cause the build to fail.
|
||||
|
||||
|
|
@ -234,3 +234,4 @@
|
|||
the new virtual machine. By default this is packer-BUILDNAME, where
|
||||
"BUILDNAME" is the name of the build. Currently, no file extension will be
|
||||
used unless it is specified in this option.
|
||||
|
||||
|
|
@ -26,3 +26,4 @@
|
|||
ARM64-64GB, ARM64-8GB, C1, C2L, C2M, C2S, START1-L,
|
||||
START1-M, START1-S, START1-XS, X64-120GB, X64-15GB, X64-30GB,
|
||||
X64-60GB
|
||||
|
||||
|
|
@ -1,3 +1,4 @@
|
|||
<!-- Code generated from the comments of the TencentCloudAccessConfig struct in builder/tencentcloud/cvm/access_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
- `skip_region_validation` (bool) - Do not check region and zone when validate.
|
||||
|
||||
|
|
@ -13,3 +13,4 @@
|
|||
- `zone` (string) - The zone where your cvm will be launch. You should
|
||||
reference Region and Zone
|
||||
for parameter taking.
|
||||
|
||||
|
|
@ -18,3 +18,4 @@
|
|||
after your image created.
|
||||
|
||||
- `skip_region_validation` (bool) - Do not check region and zone when validate.
|
||||
|
||||
|
|
@ -3,3 +3,4 @@
|
|||
- `image_name` (string) - The name you want to create your customize image,
|
||||
it should be composed of no more than 60 characters, of letters, numbers
|
||||
or minus sign.
|
||||
|
||||
|
|
@ -18,7 +18,6 @@
|
|||
type for all data disks, and each data disk size will use the origin
|
||||
value in source image.
|
||||
The data disks allow for the following argument:
|
||||
|
||||
- `disk_type` - Type of the data disk. Valid choices: `CLOUD_BASIC`, `CLOUD_PREMIUM` and `CLOUD_SSD`.
|
||||
- `disk_size` - Size of the data disk.
|
||||
- `disk_snapshot_id` - Id of the snapshot for a data disk.
|
||||
|
|
@ -53,8 +52,8 @@
|
|||
|
||||
- `host_name` (string) - host name.
|
||||
|
||||
- `run_tags` (map[string]string) - Tags to apply to the instance that is _launched_ to create the image.
|
||||
These tags are _not_ applied to the resulting image.
|
||||
- `run_tags` (map[string]string) - Tags to apply to the instance that is *launched* to create the image.
|
||||
These tags are *not* applied to the resulting image.
|
||||
|
||||
- `run_tag` ([]{name string, value string}) - Same as [`run_tags`](#run_tags) but defined as a singular repeatable
|
||||
block containing a `name` and a `value` field. In HCL2 mode the
|
||||
|
|
|
|||
|
|
@ -6,3 +6,4 @@
|
|||
- `instance_type` (string) - The instance type your cvm will be launched by.
|
||||
You should reference Instace Type
|
||||
for parameter taking.
|
||||
|
||||
|
|
@ -17,3 +17,4 @@
|
|||
of the Triton endpoint. It is useful when connecting to a temporary Triton
|
||||
installation such as Cloud-On-A-Laptop which does not generally use a
|
||||
certificate signed by a trusted root CA. The default is false.
|
||||
|
||||
|
|
@ -7,3 +7,4 @@
|
|||
pair to use for authentication with the Triton Cloud API. If
|
||||
triton_key_material is not set, it is assumed that the SSH agent has the
|
||||
private key corresponding to this key ID loaded.
|
||||
|
||||
|
|
@ -1,3 +1,2 @@
|
|||
<!-- Code generated from the comments of the AccessConfig struct in builder/triton/access_config.go; DO NOT EDIT MANUALLY -->
|
||||
|
||||
AccessConfig is for common configuration related to Triton access
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue