How to Import an Google Cloud Run Job (v2) into Terraform

Import Google Cloud Run Job (v2) with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Cloud Run resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Cloud Run Job (v2) 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_cloud_run_v2_job.etl
  id = "projects/my-project/locations/us-central1/jobs/nightly-etl"
}

Example google_cloud_run_v2_job configuration

Here is a realistic Google Cloud Run Job (v2) block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "google_cloud_run_v2_job" "etl" {
  name                = "nightly-etl"
  location            = "us-central1"
  deletion_protection = true

  template {
    template {
      containers {
        image = "us-docker.pkg.dev/my-project/jobs/etl:latest"
      }
    }
  }
}

Gotchas when importing a Google Cloud Run Job (v2)

• The schema nests template inside template; the inner template holds the containers block, which is easy to mis-indent.
• deletion_protection defaults to true in the provider and must be set false before Terraform can destroy the job.
• A Cloud Run job is not a service and has no traffic or URL; do not confuse it with google_cloud_run_v2_service.
• Job executions are runtime objects, not Terraform resources, so past or running executions are not imported.

Doing it manually with terraform import

The native approach is to write the google_cloud_run_v2_job block by hand, then run terraform import google_cloud_run_v2_job.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