How to Import an Google Regional Target HTTPS Proxy into Terraform

Import Google Regional Target HTTPS 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 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_region_target_https_proxy.main
  id = "projects/my-project/regions/us-central1/targetHttpsProxies/my-https-proxy"
}

Example google_compute_region_target_https_proxy configuration

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

resource "google_compute_region_target_https_proxy" "main" {
  name             = "my-https-proxy"
  region           = "us-central1"
  url_map          = google_compute_region_url_map.main.id
  ssl_certificates = [google_compute_region_ssl_certificate.main.id]
}

Gotchas when importing a Google Regional Target HTTPS Proxy

• Use the regional resource (projects/{project}/regions/{region}/...) here; the global equivalent is google_compute_target_https_proxy with a global path.
• Either ssl_certificates or certificate_map must be set, but they are mutually exclusive on the proxy.
• ssl_certificates must point to regional certificates (google_compute_region_ssl_certificate) in the same region, not global ones.
• Changing the region forces recreation; the proxy cannot move between regions.

Doing it manually with terraform import

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