Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit f5c9ee7

Browse files
committedJan 17, 2023
feat(batch): update the api
#### batch:v1 The following keys were added: - schemas.InstancePolicy.properties.bootDisk.$ref (Total Keys: 1)
1 parent 83da6c9 commit f5c9ee7

File tree

2 files changed

+48
-16
lines changed

2 files changed

+48
-16
lines changed
 

‎docs/dyn/batch_v1.projects.locations.jobs.html

+40-12
Original file line numberDiff line numberDiff line change
@@ -135,16 +135,23 @@ <h3>Method Details</h3>
135135
&quot;type&quot;: &quot;A String&quot;, # The accelerator type. For example, &quot;nvidia-tesla-t4&quot;. See `gcloud compute accelerator-types list`.
136136
},
137137
],
138+
&quot;bootDisk&quot;: { # A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. https://cloud.google.com/compute/docs/disks#pdspecs. https://cloud.google.com/compute/docs/disks#localssds. # Book disk to be created and attached to each VM by this InstancePolicy. Boot disk will be deleted when the VM is deleted.
139+
&quot;diskInterface&quot;: &quot;A String&quot;, # Local SSDs are available through both &quot;SCSI&quot; and &quot;NVMe&quot; interfaces. If not indicated, &quot;NVMe&quot; will be the default one for local ssds. We only support &quot;SCSI&quot; for persistent disks now.
140+
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: &quot;batch-debian&quot;: use Batch Debian images. &quot;batch-centos&quot;: use Batch CentOS images. &quot;batch-cos&quot;: use Batch Container-Optimized images.
141+
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec&#x27;s compute_resource are defined, Batch will only honor this field.
142+
&quot;snapshot&quot;: &quot;A String&quot;, # Name of a snapshot used as the data source.
143+
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type &quot;local-ssd&quot;. Persistent disks and boot disks use &quot;pd-balanced&quot;, &quot;pd-extreme&quot;, &quot;pd-ssd&quot; or &quot;pd-standard&quot;.
144+
},
138145
&quot;disks&quot;: [ # Non-boot disks to be attached for each VM created by this InstancePolicy. New disks will be deleted when the VM is deleted.
139146
{ # A new or an existing persistent disk (PD) or a local ssd attached to a VM instance.
140147
&quot;deviceName&quot;: &quot;A String&quot;, # Device name that the guest operating system will see. It is used by Runnable.volumes field to mount disks. So please specify the device_name if you want Batch to help mount the disk, and it should match the device_name field in volumes.
141148
&quot;existingDisk&quot;: &quot;A String&quot;, # Name of an existing PD.
142149
&quot;newDisk&quot;: { # A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. https://cloud.google.com/compute/docs/disks#pdspecs. https://cloud.google.com/compute/docs/disks#localssds.
143150
&quot;diskInterface&quot;: &quot;A String&quot;, # Local SSDs are available through both &quot;SCSI&quot; and &quot;NVMe&quot; interfaces. If not indicated, &quot;NVMe&quot; will be the default one for local ssds. We only support &quot;SCSI&quot; for persistent disks now.
144-
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source.
145-
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. This field is ignored if `data_source` is `disk` or `image`. If `type` is `local-ssd`, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB.
151+
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: &quot;batch-debian&quot;: use Batch Debian images. &quot;batch-centos&quot;: use Batch CentOS images. &quot;batch-cos&quot;: use Batch Container-Optimized images.
152+
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec&#x27;s compute_resource are defined, Batch will only honor this field.
146153
&quot;snapshot&quot;: &quot;A String&quot;, # Name of a snapshot used as the data source.
147-
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list` For example, &quot;pd-ssd&quot;, &quot;pd-standard&quot;, &quot;pd-balanced&quot;, &quot;local-ssd&quot;.
154+
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type &quot;local-ssd&quot;. Persistent disks and boot disks use &quot;pd-balanced&quot;, &quot;pd-extreme&quot;, &quot;pd-ssd&quot; or &quot;pd-standard&quot;.
148155
},
149156
},
150157
],
@@ -366,16 +373,23 @@ <h3>Method Details</h3>
366373
&quot;type&quot;: &quot;A String&quot;, # The accelerator type. For example, &quot;nvidia-tesla-t4&quot;. See `gcloud compute accelerator-types list`.
367374
},
368375
],
376+
&quot;bootDisk&quot;: { # A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. https://cloud.google.com/compute/docs/disks#pdspecs. https://cloud.google.com/compute/docs/disks#localssds. # Book disk to be created and attached to each VM by this InstancePolicy. Boot disk will be deleted when the VM is deleted.
377+
&quot;diskInterface&quot;: &quot;A String&quot;, # Local SSDs are available through both &quot;SCSI&quot; and &quot;NVMe&quot; interfaces. If not indicated, &quot;NVMe&quot; will be the default one for local ssds. We only support &quot;SCSI&quot; for persistent disks now.
378+
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: &quot;batch-debian&quot;: use Batch Debian images. &quot;batch-centos&quot;: use Batch CentOS images. &quot;batch-cos&quot;: use Batch Container-Optimized images.
379+
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec&#x27;s compute_resource are defined, Batch will only honor this field.
380+
&quot;snapshot&quot;: &quot;A String&quot;, # Name of a snapshot used as the data source.
381+
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type &quot;local-ssd&quot;. Persistent disks and boot disks use &quot;pd-balanced&quot;, &quot;pd-extreme&quot;, &quot;pd-ssd&quot; or &quot;pd-standard&quot;.
382+
},
369383
&quot;disks&quot;: [ # Non-boot disks to be attached for each VM created by this InstancePolicy. New disks will be deleted when the VM is deleted.
370384
{ # A new or an existing persistent disk (PD) or a local ssd attached to a VM instance.
371385
&quot;deviceName&quot;: &quot;A String&quot;, # Device name that the guest operating system will see. It is used by Runnable.volumes field to mount disks. So please specify the device_name if you want Batch to help mount the disk, and it should match the device_name field in volumes.
372386
&quot;existingDisk&quot;: &quot;A String&quot;, # Name of an existing PD.
373387
&quot;newDisk&quot;: { # A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. https://cloud.google.com/compute/docs/disks#pdspecs. https://cloud.google.com/compute/docs/disks#localssds.
374388
&quot;diskInterface&quot;: &quot;A String&quot;, # Local SSDs are available through both &quot;SCSI&quot; and &quot;NVMe&quot; interfaces. If not indicated, &quot;NVMe&quot; will be the default one for local ssds. We only support &quot;SCSI&quot; for persistent disks now.
375-
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source.
376-
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. This field is ignored if `data_source` is `disk` or `image`. If `type` is `local-ssd`, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB.
389+
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: &quot;batch-debian&quot;: use Batch Debian images. &quot;batch-centos&quot;: use Batch CentOS images. &quot;batch-cos&quot;: use Batch Container-Optimized images.
390+
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec&#x27;s compute_resource are defined, Batch will only honor this field.
377391
&quot;snapshot&quot;: &quot;A String&quot;, # Name of a snapshot used as the data source.
378-
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list` For example, &quot;pd-ssd&quot;, &quot;pd-standard&quot;, &quot;pd-balanced&quot;, &quot;local-ssd&quot;.
392+
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type &quot;local-ssd&quot;. Persistent disks and boot disks use &quot;pd-balanced&quot;, &quot;pd-extreme&quot;, &quot;pd-ssd&quot; or &quot;pd-standard&quot;.
379393
},
380394
},
381395
],
@@ -639,16 +653,23 @@ <h3>Method Details</h3>
639653
&quot;type&quot;: &quot;A String&quot;, # The accelerator type. For example, &quot;nvidia-tesla-t4&quot;. See `gcloud compute accelerator-types list`.
640654
},
641655
],
656+
&quot;bootDisk&quot;: { # A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. https://cloud.google.com/compute/docs/disks#pdspecs. https://cloud.google.com/compute/docs/disks#localssds. # Book disk to be created and attached to each VM by this InstancePolicy. Boot disk will be deleted when the VM is deleted.
657+
&quot;diskInterface&quot;: &quot;A String&quot;, # Local SSDs are available through both &quot;SCSI&quot; and &quot;NVMe&quot; interfaces. If not indicated, &quot;NVMe&quot; will be the default one for local ssds. We only support &quot;SCSI&quot; for persistent disks now.
658+
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: &quot;batch-debian&quot;: use Batch Debian images. &quot;batch-centos&quot;: use Batch CentOS images. &quot;batch-cos&quot;: use Batch Container-Optimized images.
659+
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec&#x27;s compute_resource are defined, Batch will only honor this field.
660+
&quot;snapshot&quot;: &quot;A String&quot;, # Name of a snapshot used as the data source.
661+
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type &quot;local-ssd&quot;. Persistent disks and boot disks use &quot;pd-balanced&quot;, &quot;pd-extreme&quot;, &quot;pd-ssd&quot; or &quot;pd-standard&quot;.
662+
},
642663
&quot;disks&quot;: [ # Non-boot disks to be attached for each VM created by this InstancePolicy. New disks will be deleted when the VM is deleted.
643664
{ # A new or an existing persistent disk (PD) or a local ssd attached to a VM instance.
644665
&quot;deviceName&quot;: &quot;A String&quot;, # Device name that the guest operating system will see. It is used by Runnable.volumes field to mount disks. So please specify the device_name if you want Batch to help mount the disk, and it should match the device_name field in volumes.
645666
&quot;existingDisk&quot;: &quot;A String&quot;, # Name of an existing PD.
646667
&quot;newDisk&quot;: { # A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. https://cloud.google.com/compute/docs/disks#pdspecs. https://cloud.google.com/compute/docs/disks#localssds.
647668
&quot;diskInterface&quot;: &quot;A String&quot;, # Local SSDs are available through both &quot;SCSI&quot; and &quot;NVMe&quot; interfaces. If not indicated, &quot;NVMe&quot; will be the default one for local ssds. We only support &quot;SCSI&quot; for persistent disks now.
648-
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source.
649-
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. This field is ignored if `data_source` is `disk` or `image`. If `type` is `local-ssd`, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB.
669+
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: &quot;batch-debian&quot;: use Batch Debian images. &quot;batch-centos&quot;: use Batch CentOS images. &quot;batch-cos&quot;: use Batch Container-Optimized images.
670+
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec&#x27;s compute_resource are defined, Batch will only honor this field.
650671
&quot;snapshot&quot;: &quot;A String&quot;, # Name of a snapshot used as the data source.
651-
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list` For example, &quot;pd-ssd&quot;, &quot;pd-standard&quot;, &quot;pd-balanced&quot;, &quot;local-ssd&quot;.
672+
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type &quot;local-ssd&quot;. Persistent disks and boot disks use &quot;pd-balanced&quot;, &quot;pd-extreme&quot;, &quot;pd-ssd&quot; or &quot;pd-standard&quot;.
652673
},
653674
},
654675
],
@@ -928,16 +949,23 @@ <h3>Method Details</h3>
928949
&quot;type&quot;: &quot;A String&quot;, # The accelerator type. For example, &quot;nvidia-tesla-t4&quot;. See `gcloud compute accelerator-types list`.
929950
},
930951
],
952+
&quot;bootDisk&quot;: { # A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. https://cloud.google.com/compute/docs/disks#pdspecs. https://cloud.google.com/compute/docs/disks#localssds. # Book disk to be created and attached to each VM by this InstancePolicy. Boot disk will be deleted when the VM is deleted.
953+
&quot;diskInterface&quot;: &quot;A String&quot;, # Local SSDs are available through both &quot;SCSI&quot; and &quot;NVMe&quot; interfaces. If not indicated, &quot;NVMe&quot; will be the default one for local ssds. We only support &quot;SCSI&quot; for persistent disks now.
954+
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: &quot;batch-debian&quot;: use Batch Debian images. &quot;batch-centos&quot;: use Batch CentOS images. &quot;batch-cos&quot;: use Batch Container-Optimized images.
955+
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec&#x27;s compute_resource are defined, Batch will only honor this field.
956+
&quot;snapshot&quot;: &quot;A String&quot;, # Name of a snapshot used as the data source.
957+
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type &quot;local-ssd&quot;. Persistent disks and boot disks use &quot;pd-balanced&quot;, &quot;pd-extreme&quot;, &quot;pd-ssd&quot; or &quot;pd-standard&quot;.
958+
},
931959
&quot;disks&quot;: [ # Non-boot disks to be attached for each VM created by this InstancePolicy. New disks will be deleted when the VM is deleted.
932960
{ # A new or an existing persistent disk (PD) or a local ssd attached to a VM instance.
933961
&quot;deviceName&quot;: &quot;A String&quot;, # Device name that the guest operating system will see. It is used by Runnable.volumes field to mount disks. So please specify the device_name if you want Batch to help mount the disk, and it should match the device_name field in volumes.
934962
&quot;existingDisk&quot;: &quot;A String&quot;, # Name of an existing PD.
935963
&quot;newDisk&quot;: { # A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. https://cloud.google.com/compute/docs/disks#pdspecs. https://cloud.google.com/compute/docs/disks#localssds.
936964
&quot;diskInterface&quot;: &quot;A String&quot;, # Local SSDs are available through both &quot;SCSI&quot; and &quot;NVMe&quot; interfaces. If not indicated, &quot;NVMe&quot; will be the default one for local ssds. We only support &quot;SCSI&quot; for persistent disks now.
937-
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source.
938-
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. This field is ignored if `data_source` is `disk` or `image`. If `type` is `local-ssd`, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB.
965+
&quot;image&quot;: &quot;A String&quot;, # Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: &quot;batch-debian&quot;: use Batch Debian images. &quot;batch-centos&quot;: use Batch CentOS images. &quot;batch-cos&quot;: use Batch Container-Optimized images.
966+
&quot;sizeGb&quot;: &quot;A String&quot;, # Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec&#x27;s compute_resource are defined, Batch will only honor this field.
939967
&quot;snapshot&quot;: &quot;A String&quot;, # Name of a snapshot used as the data source.
940-
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list` For example, &quot;pd-ssd&quot;, &quot;pd-standard&quot;, &quot;pd-balanced&quot;, &quot;local-ssd&quot;.
968+
&quot;type&quot;: &quot;A String&quot;, # Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type &quot;local-ssd&quot;. Persistent disks and boot disks use &quot;pd-balanced&quot;, &quot;pd-extreme&quot;, &quot;pd-ssd&quot; or &quot;pd-standard&quot;.
941969
},
942970
},
943971
],

‎googleapiclient/discovery_cache/documents/batch.v1.json

+8-4
Original file line numberDiff line numberDiff line change
@@ -643,7 +643,7 @@
643643
}
644644
}
645645
},
646-
"revision": "20221214",
646+
"revision": "20230105",
647647
"rootUrl": "https://batch.googleapis.com/",
648648
"schemas": {
649649
"Accelerator": {
@@ -1068,11 +1068,11 @@
10681068
"type": "string"
10691069
},
10701070
"image": {
1071-
"description": "Name of a public or custom image used as the data source.",
1071+
"description": "Name of a public or custom image used as the data source. For example, the following are all valid URLs: (1) Specify the image by its family name: projects/{project}/global/images/family/{image_family} (2) Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: \"batch-debian\": use Batch Debian images. \"batch-centos\": use Batch CentOS images. \"batch-cos\": use Batch Container-Optimized images.",
10721072
"type": "string"
10731073
},
10741074
"sizeGb": {
1075-
"description": "Disk size in GB. This field is ignored if `data_source` is `disk` or `image`. If `type` is `local-ssd`, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB.",
1075+
"description": "Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec's compute_resource are defined, Batch will only honor this field.",
10761076
"format": "int64",
10771077
"type": "string"
10781078
},
@@ -1081,7 +1081,7 @@
10811081
"type": "string"
10821082
},
10831083
"type": {
1084-
"description": "Disk type as shown in `gcloud compute disk-types list` For example, \"pd-ssd\", \"pd-standard\", \"pd-balanced\", \"local-ssd\".",
1084+
"description": "Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type \"local-ssd\". Persistent disks and boot disks use \"pd-balanced\", \"pd-extreme\", \"pd-ssd\" or \"pd-standard\".",
10851085
"type": "string"
10861086
}
10871087
},
@@ -1163,6 +1163,10 @@
11631163
},
11641164
"type": "array"
11651165
},
1166+
"bootDisk": {
1167+
"$ref": "Disk",
1168+
"description": "Book disk to be created and attached to each VM by this InstancePolicy. Boot disk will be deleted when the VM is deleted."
1169+
},
11661170
"disks": {
11671171
"description": "Non-boot disks to be attached for each VM created by this InstancePolicy. New disks will be deleted when the VM is deleted.",
11681172
"items": {

0 commit comments

Comments
 (0)
Please sign in to comment.