Google CloudGoogle Container Registrygoogle_container_registryPro

How to Import an Google Container Registry into Terraform

To import an existing Google Container Registry into Terraform, scan it with Terraback and run terraback gcp import --method bulk. Terraback writes the matching google_container_registry resource block and the Terraform 1.5+ import block for you, so you do not have to run terraform import by hand. The import ID is the project ID that owns the registry (for example, my-project).

Import Google Container Registry with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Google Container Registry resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Container Registry to managed Terraform.

1

Scan your Google Cloud account

terraback scan all gcp --project my-gcp-project
2

Generate import blocks and import into state

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_container_registry.registry
  id = "my-project"
}

Example google_container_registry configuration

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

resource "google_container_registry" "registry" {
  location = "US"
}

Gotchas when importing a Google Container Registry

  • This resource does not create a registry directly; it provisions and manages the backing Cloud Storage bucket (for example artifacts.my-project.appspot.com) that GCR uses.
  • location is the GCR multi-region (US, EU, or ASIA) and is immutable; it determines the bucket name and cannot be changed in place.
  • Container Registry is deprecated by Google in favor of Artifact Registry; for new work use google_artifact_registry_repository instead.
  • Pushing and pulling images is controlled by IAM on the storage bucket, which is managed separately from this resource.

Doing it manually with terraform import

The native approach is to write the google_container_registry block by hand, then run terraform import google_container_registry.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 your whole Google Cloud account in minutes

Terraback scans 80+ Google Cloud resource types and emits clean Terraform plus import blocks, running locally with read-only credentials. $499 once, no SaaS.