How to Import an Google Compute Target HTTP Proxy into Terraform

Import Google Compute Target HTTP Proxy with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Google Cloud Load Balancing resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Compute 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_target_http_proxy.web
  id = "projects/my-project/global/targetHttpProxies/web-proxy"
}

Example google_compute_target_http_proxy configuration

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

resource "google_compute_target_http_proxy" "web" {
  name    = "web-proxy"
  url_map = google_compute_url_map.web.id
}

Gotchas when importing a Google Compute Target HTTP Proxy

• This is the global proxy; the import path contains /global/. Regional internal load balancers use google_compute_region_target_http_proxy instead.
• url_map is required and references a separate google_compute_url_map that is not imported with the proxy.
• A target HTTP proxy only carries HTTP traffic; for HTTPS use google_compute_target_https_proxy, which adds SSL certificates.
• The proxy is not reachable until a google_compute_global_forwarding_rule points a frontend IP and port at it.

Doing it manually with terraform import

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