How to Import an Google Certificate Manager Certificate Map into Terraform

Import Google Certificate Manager Certificate Map with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Google Certificate Manager resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Certificate Manager Certificate Map 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_certificate_manager_certificate_map.main
  id = "projects/my-project/locations/global/certificateMaps/my-cert-map"
}

Example google_certificate_manager_certificate_map configuration

Here is a realistic Google Certificate Manager Certificate Map block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "google_certificate_manager_certificate_map" "main" {
  name        = "my-cert-map"
  description = "Production certificate map"
  labels = {
    env = "prod"
  }
}

Gotchas when importing a Google Certificate Manager Certificate Map

• Certificate maps are global, so the location segment in the import ID is always global.
• Map entries (google_certificate_manager_certificate_map_entry) are separate resources and are not imported with the map.
• A map referenced by a target HTTPS proxy cannot be deleted until the proxy stops using it.
• Terraback emits a lifecycle prevent_destroy block on this resource; remove it if you intend to let Terraform delete the map.

Doing it manually with terraform import

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