How to Import an Google Compute URL Map into Terraform
terraback gcp import --method bulk. Terraback writes the matching google_compute_url_map resource block and the Terraform 1.5+ import block for you, so you do not have to run terraform import by hand. The import ID is the full path projects/{project}/global/urlMaps/{name} (for example, projects/my-project/global/urlMaps/web-map).Import Google Compute URL Map with Terraback (recommended)
Terraback reverse-engineers your live infrastructure: it reads the Compute Engine resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Compute URL Map to managed Terraform.
Scan your Google Cloud account
terraback scan all gcp --project my-gcp-projectGenerate import blocks and import into state
terraback gcp import --method bulkThe 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_url_map.web
id = "projects/my-project/global/urlMaps/web-map"
}Example google_compute_url_map configuration
Here is a realistic Google Compute URL Map block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.
resource "google_compute_url_map" "web" {
name = "web-map"
default_service = google_compute_backend_service.web.id
}Gotchas when importing a Google Compute URL Map
- google_compute_url_map is global; a regional internal load balancer uses the separate google_compute_region_url_map resource.
- default_service or default_url_redirect is required; host_rule and path_matcher blocks must be copied exactly to preserve routing.
- Backend services and buckets referenced by the map are separate resources you should import alongside it.
- A URL map used purely for HTTP-to-HTTPS redirects sets default_url_redirect instead of default_service.
Doing it manually with terraform import
The native approach is to write the google_compute_url_map block by hand, then run terraform import google_compute_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
Import your whole Google Cloud account in minutes
Terraback scans 80+ Google Cloud resource types and emits clean Terraform plus import blocks, running locally with read-only credentials. $499 once, no SaaS.