How to Import an Google Eventarc Trigger into Terraform

Import Google Eventarc Trigger with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Google Eventarc resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Eventarc Trigger 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_eventarc_trigger.on_object
  id = "projects/my-project/locations/us-central1/triggers/on-object"
}

Example google_eventarc_trigger configuration

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

resource "google_eventarc_trigger" "on_object" {
  name            = "on-object"
  location        = "us-central1"
  service_account = "eventarc-sa@my-project.iam.gserviceaccount.com"

  matching_criteria {
    attribute = "type"
    value     = "google.cloud.storage.object.v1.finalized"
  }

  destination {
    cloud_run_service {
      service = "handler"
      region  = "us-central1"
    }
  }
}

Gotchas when importing a Google Eventarc Trigger

• Every matching_criteria attribute/value pair is part of the filter; reproduce all of them exactly or the trigger matches different events after apply.
• The service_account needs roles like eventarc.eventReceiver and (for Pub/Sub transport) iam.serviceAccountTokenCreator, granted via separate IAM resources.
• destination must point at an existing target (Cloud Run service, Cloud Function, Workflow, or GKE service); the trigger does not create that target.
• For some event providers a backing Pub/Sub topic and subscription are created automatically and surface under the transport block.

Doing it manually with terraform import

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