gcloud alpha spanner migration schema - migrate schema from a source database to Cloud Spanner
gcloud alpha spanner migration schema --source=SOURCE [--dry-run] [--log-level=LOG_LEVEL] [--prefix=PREFIX] [--source-profile=SOURCE_PROFILE] [--target=TARGET] [--target-profile=TARGET_PROFILE] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Migrate schema from a source database to Cloud Spanner.
To generate schema file from the source database:
$ gcloud alpha spanner migration schema --source=postgresql < \ ~/cart.pg_dump
- --source=SOURCE
Flag for specifying source database (e.g., PostgreSQL, MySQL, DynamoDB).
- --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").
- --target-profile=TARGET_PROFILE
Flag for specifying connection profile for target database (e.g., "dialect=postgresql)".
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.
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.