How to Import an Google Cloud Run Service into Terraform

Import Google Cloud Run Service 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 Service 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_service.api
  id = "us-central1/my-project/api"
}

Example google_cloud_run_service configuration

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

resource "google_cloud_run_service" "api" {
  name     = "api"
  project  = "my-project"
  location = "us-central1"

  template {
    spec {
      containers {
        image = "us-docker.pkg.dev/my-project/web/api:latest"
      }
    }
  }
}

Gotchas when importing a Google Cloud Run Service

• google_cloud_run_service is the Knative-style (v1) resource; the newer google_cloud_run_v2_service uses a different schema and import path.
• The import ID uses location/project/name, not a projects/... global path; the location is a region such as us-central1.
• Public access (allUsers invoker) is a separate google_cloud_run_service_iam_member or _iam_policy resource, not imported with the service.
• Server-managed annotations like the latest revision name and serving status reappear on plan; ignore_changes on metadata.0.annotations is often needed.

Doing it manually with terraform import

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