How to Import an Google Regional URL Map into Terraform

Import Google Regional URL Map with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Google Compute Engine resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Regional URL Map 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_compute_region_url_map.main
  id = "projects/my-project/regions/us-central1/urlMaps/my-url-map"
}

Example google_compute_region_url_map configuration

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

resource "google_compute_region_url_map" "main" {
  name            = "my-url-map"
  region          = "us-central1"
  default_service = google_compute_region_backend_service.main.id

  host_rule {
    hosts        = ["example.com"]
    path_matcher = "main"
  }

  path_matcher {
    name            = "main"
    default_service = google_compute_region_backend_service.main.id
  }
}

Gotchas when importing a Google Regional URL Map

• This is the regional URL map (regions/{region} in the import path); the global google_compute_url_map uses a global path.
• Regional URL maps reference google_compute_region_backend_service, not global backend services.
• default_service and a default_url_redirect are mutually exclusive; set exactly one.
• Every path_matcher named in a host_rule must have a matching path_matcher block, or validation fails.

Doing it manually with terraform import

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