You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@
5
5
* Added `workspace_url` attribute to the `databricks_current_user` data source ([#1107](https://github.com/databrickslabs/terraform-provider-databricks/pull/1107)).
6
6
* Fixed issue at `databricks_mount` where new cluster was created for S3 mount even when `cluster_id` was specified ([#1064](https://github.com/databrickslabs/terraform-provider-databricks/issues/1064)).
7
7
* Allow to disable auto-termination for Databricks SQL endpoints ([#900](https://github.com/databrickslabs/terraform-provider-databricks/pull/900)).
8
+
* Added new `gcp_attributes` to `databricks_cluster` and `databricks_instance_pool` ([#1126](https://github.com/databrickslabs/terraform-provider-databricks/pull/1126)).
Copy file name to clipboardExpand all lines: docs/resources/cluster.md
+27-2
Original file line number
Diff line number
Diff line change
@@ -317,7 +317,7 @@ The following options are available:
317
317
318
318
`azure_attributes` optional configuration block contains attributes related to [clusters running on Azure](https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/clusters#--azureattributes).
319
319
320
-
Here is the example of shared autoscaling cluster with some of AWS options set:
320
+
Here is the example of shared autoscaling cluster with some of Azure options set:
321
321
322
322
```hcl
323
323
data "databricks_spark_version" "latest" {}
@@ -351,10 +351,35 @@ The following options are [available](https://docs.microsoft.com/en-us/azure/dat
351
351
352
352
`gcp_attributes` optional configuration block contains attributes related to [clusters running on GCP](https://docs.gcp.databricks.com/dev-tools/api/latest/clusters.html#clustergcpattributes).
353
353
354
+
Here is the example of shared autoscaling cluster with some of GCP options set:
*`use_preemptible_executors` - (Optional, bool) if we should use preemptible executors ([GCP documentation](https://cloud.google.com/compute/docs/instances/preemptible))
375
+
*`use_preemptible_executors` - (Optional, bool) if we should use preemptible executors ([GCP documentation](https://cloud.google.com/compute/docs/instances/preemptible)). *Warning: this field is deprecated in favor of `availability`, and will be removed soon.*
357
376
*`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.
377
+
*`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`.
378
+
*`boot_disk_size` (optional, int) Boot disk size in GB
379
+
*`zone_id` (optional) Identifier for the availability zone in which the cluster resides. This can be one of the following:
380
+
*`HA` (default): High availability, spread nodes across availability zones for a Databricks deployment region.
381
+
*`AUTO`: Databricks picks an availability zone to schedule the cluster on.
382
+
* name of a GCP availability zone: pick one of the available zones from the [list of available availability zones](https://cloud.google.com/compute/docs/regions-zones#available).
Copy file name to clipboardExpand all lines: docs/resources/instance_pool.md
+9-1
Original file line number
Diff line number
Diff line change
@@ -61,9 +61,17 @@ The following options are [available](https://docs.databricks.com/dev-tools/api/
61
61
62
62
The following options are [available](https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/clusters#--azureattributes):
63
63
64
-
*`availability` - (Optional) Availability type used for all subsequent nodes past the `first_on_demand` ones. Valid values are `SPOT_AZURE` and `ON_DEMAND_AZURE`.
64
+
*`availability` - (Optional) Availability type used for all nodes. Valid values are `SPOT_AZURE` and `ON_DEMAND_AZURE`.
65
65
*`spot_bid_max_price` - (Optional) The max price for Azure spot instances. Use `-1` to specify lowest price.
66
66
67
+
## gcp_attributes Configuration Block
68
+
69
+
`gcp_attributes` optional configuration block contains attributes related to [instance pools on GCP](https://docs.gcp.databricks.com/dev-tools/api/latest/instance-pools.html#clusterinstancepoolgcpattributes).
70
+
71
+
The following options are [available](https://docs.gcp.databricks.com/dev-tools/api/latest/clusters.html#gcpavailability):
72
+
73
+
*`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`.
0 commit comments