How to Import an Google Cloud Dataproc Cluster into Terraform

Import Google Cloud Dataproc Cluster with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Cloud Dataproc resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Cloud Dataproc Cluster to managed Terraform.

terraback scan all gcp --project my-gcp-project

terraback gcp import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

import {
  to = google_dataproc_cluster.analytics
  id = "projects/my-project/regions/us-central1/clusters/analytics"
}

Example google_dataproc_cluster configuration

Here is a realistic Google Cloud Dataproc Cluster block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "google_dataproc_cluster" "analytics" {
  name    = "analytics"
  region  = "us-central1"
  project = "my-project"

  cluster_config {
    master_config {
      num_instances = 1
      machine_type  = "n1-standard-4"
    }
    worker_config {
      num_instances = 2
      machine_type  = "n1-standard-4"
    }
  }
}

Gotchas when importing a Google Cloud Dataproc Cluster

• Dataproc clusters are regional; the import path uses regions/<region>, and region is required in HCL.
• Most cluster_config fields are immutable, so changing machine types or disk config forces a destroy and recreate.
• Staging and temp buckets default to auto-created GCS buckets; pin them explicitly if you want stable names.
• Jobs submitted to the cluster are runtime objects and are not imported as Terraform resources.

Doing it manually with terraform import

The native approach is to write the google_dataproc_cluster block by hand, then run terraform import google_dataproc_cluster.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import other Google Cloud resources