How to Import an Google Compute Target HTTPS Proxy into Terraform

Import Google Compute Target HTTPS Proxy 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 Target HTTPS 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_https_proxy.web
  id = "projects/my-project/global/targetHttpsProxies/web-proxy"
}

Example google_compute_target_https_proxy configuration

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

resource "google_compute_target_https_proxy" "web" {
  name             = "web-proxy"
  url_map          = google_compute_url_map.web.id
  ssl_certificates = [google_compute_ssl_certificate.web.id]
}

Gotchas when importing a Google Compute Target HTTPS Proxy

• google_compute_target_https_proxy is global; a regional internal HTTPS load balancer uses the separate google_compute_region_target_https_proxy resource.
• url_map and ssl_certificates reference existing resources by self link; import those too or the plan will be incomplete.
• Newer setups attach a certificate_map instead of a static ssl_certificates list; use whichever the proxy actually has.
• ssl_policy is optional but, if set on the live proxy, must be included to avoid a diff that weakens TLS settings.

Doing it manually with terraform import

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