gcloud alpha spanner migrate schema

NAME

gcloud alpha spanner migrate schema - migrate schema from a source database to Cloud Spanner

SYNOPSIS

gcloud alpha spanner migrate schema --source=SOURCE --target-profile=TARGET_PROFILE [--dry-run] [--log-level=LOG_LEVEL] [--prefix=PREFIX] [--source-profile=SOURCE_PROFILE] [--target=TARGET] [GCLOUD_WIDE_FLAG …]

DESCRIPTION

(ALPHA) Migrate schema from a source database to Cloud Spanner.

EXAMPLES

To generate schema file from the source database:

gcloud alpha spanner migrate schema --source=postgresql < ~/cart.pg_dump

REQUIRED FLAGS

--source=SOURCE

Flag for specifying source database (e.g., PostgreSQL, MySQL, DynamoDB).

--target-profile=TARGET_PROFILE

Flag for specifying connection profile for target database (e.g., "dialect=postgresql)".

OPTIONAL FLAGS

--dry-run

Flag for generating DDL and schema conversion report without creating a Cloud Spanner database.

--log-level=LOG_LEVEL

To configure the log level for the execution (INFO, VERBOSE).

--prefix=PREFIX

File prefix for generated files.

--source-profile=SOURCE_PROFILE

Flag for specifying connection profile for source database (e.g., "file=<path>,format=dump").

--target=TARGET

Specifies the target database, defaults to Spanner (accepted values: Spanner) (default "Spanner").

GCLOUD WIDE FLAGS

These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.

Run $ gcloud help for details.

NOTES

This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist.