Add field metastore_config to google_dataproc_cluster (#5146) (#9935)

* added metastoreConfig to dataproc cluster * Update mmv1/third_party/terraform/resources/resource_dataproc_cluster.go.erb Co-authored-by: Cameron Thornton <[email protected]> Co-authored-by: Cameron Thornton <[email protected]> Signed-off-by: Modular Magician <[email protected]> Co-authored-by: Cameron Thornton <[email protected]>
hashicorp · Aug 27, 2021 · 39dd0ed · 39dd0ed
1 parent 6658601
commit 39dd0ed
Show file tree

Hide file tree

Showing 2 changed files with 24 additions and 0 deletions.
diff --git a/.changelog/5146.txt b/.changelog/5146.txt
@@ -0,0 +1,3 @@
+```release-note:enhancement
+dataproc: added field `metastore_config` to `google_dataproc_cluster` (beta)
+```
diff --git a/website/docs/r/dataproc_cluster.html.markdown b/website/docs/r/dataproc_cluster.html.markdown
@@ -163,6 +163,7 @@ The `cluster_config` block supports:
         initialization_action     { ... }
         encryption_config         { ... }
         endpoint_config           { ... }
+        metastore_config          { ... }
     }
 ```
 
@@ -214,6 +215,9 @@ The `cluster_config` block supports:
 
 * `endpoint_config` (Optional, Beta) The config settings for port access on the cluster.
    Structure defined below.
+
+* `metastore_config` (Optional, Beta) The config setting for metastore service with the cluster.
+   Structure defined below.
 - - -
 
 The `cluster_config.gce_cluster_config` block supports:
@@ -650,6 +654,23 @@ cluster_config {
 * `enable_http_port_access` - (Optional) The flag to enable http access to specific ports
   on the cluster from external sources (aka Component Gateway). Defaults to false.
 
+
+The `metastore_config` block (Optional, Computed, Beta) supports:
+
+```hcl
+cluster_config {
+  metastore_config {
+    dataproc_metastore_service = "projects/projectId/locations/region/services/serviceName"
+  }
+}
+```
+
+* `dataproc_metastore_service` - (Required) Resource name of an existing Dataproc Metastore service.
+
+Only resource names including projectid and location (region) are valid. Examples:
+
+`projects/[projectId]/locations/[dataproc_region]/services/[service-name]`
+
 ## Attributes Reference
 
 In addition to the arguments listed above, the following computed attributes are