Google CloudCloud Spannergoogle_spanner_databasePro

How to Import an Google Cloud Spanner Database into Terraform

To import an existing Google Cloud Spanner Database into Terraform, scan it with Terraback and run terraback gcp import --method bulk. Terraback writes the matching google_spanner_database 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 full path projects/{project}/instances/{instance}/databases/{name}, or the slash form {instance}/{name} (for example, projects/my-project/instances/prod-spanner/databases/orders).

Import Google Cloud Spanner Database with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Cloud Spanner resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Google Cloud Spanner Database 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_spanner_database.orders
  id = "projects/my-project/instances/prod-spanner/databases/orders"
}

Example google_spanner_database configuration

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

resource "google_spanner_database" "orders" {
  name                = "orders"
  instance            = "prod-spanner"
  database_dialect    = "GOOGLE_STANDARD_SQL"
  deletion_protection = true
}

Gotchas when importing a Google Cloud Spanner Database

  • The import ID includes the parent instance; that google_spanner_instance must already exist in the config.
  • deletion_protection defaults to true and must be set false before Terraform can destroy the database.
  • ddl statements applied through Terraform are append-only; the provider does not reconcile or remove existing schema on import.
  • database_dialect (GOOGLE_STANDARD_SQL vs POSTGRESQL) is fixed at creation and cannot be changed.

Doing it manually with terraform import

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