1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 12:22:03 +00:00
gcloud-help/gcloud/alpha/spanner/instances/move

80 lines
3.2 KiB
Text
Raw Normal View History

2024-04-17 09:40:58 +00:00
NAME
gcloud alpha spanner instances move - move the Cloud Spanner instance to
2025-02-12 10:41:39 +00:00
the specified instance configuration
2024-04-17 09:40:58 +00:00
SYNOPSIS
gcloud alpha spanner instances move INSTANCE --target-config=TARGET_CONFIG
2025-02-12 10:41:39 +00:00
[--target-database-move-configs=[^:^database-id=DATABASE_ID:kms-key-names=KEY1,
2025-01-29 10:02:21 +00:00
KEY2,...]] [GCLOUD_WIDE_FLAG ...]
2024-04-17 09:40:58 +00:00
DESCRIPTION
2025-02-12 10:41:39 +00:00
(ALPHA) Move the Cloud Spanner instance to the specified instance
configuration.
2024-04-17 09:40:58 +00:00
EXAMPLES
2025-02-12 10:41:39 +00:00
To move the Cloud Spanner instance, which has two CMEK-enabled databases
db1 and db2 and a database db3 with Google-managed encryption keys, to the
target instance configuration nam3 (us-east4, us-east1, us-central1), run: $ gcloud alpha spanner instances move my-instance-id \
2025-01-29 10:02:21 +00:00
--target-config=nam3 \
2025-02-12 10:41:39 +00:00
--target-database-move-configs=^:^database-id=db1:kms-key-names=\
projects/myproject/locations/us-east4/keyRings/mykeyring/\
cryptoKeys/cmek-key,projects/myproject/locations/us-east1/keyRings/\
mykeyring/cryptoKeys/cmek-key,projects/myproject/locations/\
us-central1/keyRings/mykeyring/cryptoKeys/cmek-key \
--target-database-move-configs=^:^database-id=db2:kms-key-names=\
projects/myproject/locations/us-east4/keyRings/mykeyring/\
cryptoKeys/cmek-key,projects/myproject/locations/us-east1/keyRings/\
mykeyring/cryptoKeys/cmek-key,projects/myproject/locations/\
us-central1/keyRings/mykeyring/cryptoKeys/cmek-key
2024-04-17 09:40:58 +00:00
POSITIONAL ARGUMENTS
INSTANCE
Cloud Spanner instance ID.
REQUIRED FLAGS
--target-config=TARGET_CONFIG
Target Instance configuration to move the instances.
2025-01-29 10:02:21 +00:00
OPTIONAL FLAGS
2025-02-12 10:41:39 +00:00
--target-database-move-configs=[^:^database-id=DATABASE_ID:kms-key-names=KEY1,KEY2,...]
2025-01-29 10:02:21 +00:00
Database level configurations for each database to be moved. Currently
2025-02-12 10:41:39 +00:00
only used for CMEK-enabled databases to specificy the target database
KMS keys. Sets target_database_move_configs value.
2025-01-29 10:02:21 +00:00
database-id
2025-05-14 10:45:02 +00:00
Required, sets database-id value.
2025-01-29 10:02:21 +00:00
2025-02-12 10:41:39 +00:00
kms-key-names
Sets kms-key-names value.
2025-01-29 10:02:21 +00:00
Shorthand Example:
2025-02-12 10:41:39 +00:00
--target-database-move-configs=database-id=string,kms-key-names=string --target-database-move-configs=database-id=string,kms-key-names=string
2025-01-29 10:02:21 +00:00
JSON Example:
2025-02-12 10:41:39 +00:00
--target-database-move-configs='[{"database-id": "string", "kms-key-names": "string"}]'
2025-01-29 10:02:21 +00:00
File Example:
--target-database-move-configs=path_to_file.(yaml|json)
2024-04-17 09:40:58 +00:00
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. These variants are also available:
$ gcloud spanner instances move
$ gcloud beta spanner instances move