fix!: Remove temp_bucket from VirtualClusterConfig, as its value was not used

Google APIs · copybara-github · commit afc5066d9c31 · 2022-04-07T16:08:43.000-07:00
Committer: @Harwayne PiperOrigin-RevId: 440224385
diff --git a/google/cloud/dataproc/v1/clusters.proto b/google/cloud/dataproc/v1/clusters.proto
@@ -303,21 +303,6 @@ message VirtualClusterConfig {
   // a Cloud Storage bucket.**
   string staging_bucket = 1 [(google.api.field_behavior) = OPTIONAL];
 
-  // Optional. A Cloud Storage bucket used to store ephemeral cluster and jobs data,
-  // such as Spark and MapReduce history files.
-  // If you do not specify a temp bucket,
-  // Dataproc will determine a Cloud Storage location (US,
-  // ASIA, or EU) for your cluster's temp bucket according to the
-  // Compute Engine zone where your cluster is deployed, and then create
-  // and manage this project-level, per-location bucket. The default bucket has
-  // a TTL of 90 days, but you can use any TTL (or none) if you specify a
-  // bucket (see
-  // [Dataproc staging and temp
-  // buckets](https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/staging-bucket)).
-  // **This field requires a Cloud Storage bucket name, not a `gs://...` URI to
-  // a Cloud Storage bucket.**
-  string temp_bucket = 2 [(google.api.field_behavior) = OPTIONAL];
-
   oneof infrastructure_config {
     // Required. The configuration for running the Dataproc cluster on Kubernetes.
     KubernetesClusterConfig kubernetes_cluster_config = 6 [(google.api.field_behavior) = REQUIRED];
