How to Import an Google Cloud Functions (2nd gen) into Terraform

Import Google Cloud Functions (2nd gen) with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Cloud Functions resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Cloud Functions (2nd gen) 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_cloudfunctions2_function.process
  id = "projects/my-project/locations/us-central1/functions/process-events"
}

Example google_cloudfunctions2_function configuration

Here is a realistic Google Cloud Functions (2nd gen) block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "google_cloudfunctions2_function" "process" {
  name     = "process-events"
  location = "us-central1"

  build_config {
    runtime     = "python312"
    entry_point = "handler"
  }

  service_config {
    max_instance_count = 10
    available_memory   = "256M"
    timeout_seconds    = 60
  }
}

Gotchas when importing a Google Cloud Functions (2nd gen)

• This is the 2nd gen resource (google_cloudfunctions2_function); 1st gen functions use the separate google_cloudfunctions_function type and a different import path.
• The source archive in build_config.source.storage_source must point at a bucket object that still exists, or the next apply fails to rebuild.
• A 2nd gen function is backed by a Cloud Run service; IAM for invocation is set on the underlying Cloud Run service, not the function.
• event_trigger.pubsub_topic and service account fields are not always fully returned; verify them against the console after import.

Doing it manually with terraform import

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