How to Import an Google Regional Target HTTP Proxy into Terraform

Import Google Regional Target HTTP Proxy 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 Target HTTP Proxy 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_target_http_proxy.main
  id = "projects/my-project/regions/us-central1/targetHttpProxies/my-http-proxy"
}

Example google_compute_region_target_http_proxy configuration

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

resource "google_compute_region_target_http_proxy" "main" {
  name    = "my-http-proxy"
  region  = "us-central1"
  url_map = google_compute_region_url_map.main.id
}

Gotchas when importing a Google Regional Target HTTP Proxy

• This is the regional proxy; its import path includes regions/{region}, unlike the global google_compute_target_http_proxy which uses global.
• The url_map must reference a google_compute_region_url_map in the same region, not a global URL map.
• Changing the region forces recreation; the proxy cannot be moved between regions.
• Terraback emits a lifecycle prevent_destroy block; remove it if you want Terraform to be able to delete the proxy.

Doing it manually with terraform import

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