Added gcp_attributes.local_ssd_count to databricks_cluster resource

New setting allows to specify number of local SSD disks to be attached to each node
databricks · Aug 2, 2023 · 1993b34 · 1993b34
1 parent 160b944
commit 1993b34
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/clusters/clusters_api.go b/clusters/clusters_api.go
@@ -171,6 +171,7 @@ type GcpAttributes struct {
 	Availability            Availability `json:"availability,omitempty"`
 	BootDiskSize            int32        `json:"boot_disk_size,omitempty"`
 	ZoneId                  string       `json:"zone_id,omitempty"`
+	LocalSsdCount           int32        `json:"local_ssd_count,omitempty"`
 }
 
 // DbfsStorageInfo contains the destination string for DBFS

diff --git a/docs/resources/cluster.md b/docs/resources/cluster.md
@@ -424,6 +424,7 @@ The following options are available:
 * `google_service_account` - (Optional, string) Google Service Account email address that the cluster uses to authenticate with Google Identity. This field is used for authentication with the GCS and BigQuery data sources.
 * `availability` - (Optional) Availability type used for all nodes. Valid values are `PREEMPTIBLE_GCP`, `PREEMPTIBLE_WITH_FALLBACK_GCP` and `ON_DEMAND_GCP`, default: `ON_DEMAND_GCP`.
 * `boot_disk_size` (optional, int) Boot disk size in GB
+* `local_ssd_count` (optional, int) Number of local SSD disks (each is 375GB in size) that will be attached to each node of the cluster. 
 * `zone_id` (optional)  Identifier for the availability zone in which the cluster resides. This can be one of the following:
   * `HA` (default): High availability, spread nodes across availability zones for a Databricks deployment region.
   * `AUTO`: Databricks picks an availability zone to schedule the cluster on.