mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 06:47:12 +00:00
gcloud: Wed Jan 29 10:02:21 UTC 2025
This commit is contained in:
parent
861d4011dc
commit
50090ced80
157 changed files with 5563 additions and 179 deletions
|
|
@ -4,15 +4,27 @@ NAME
|
|||
|
||||
SYNOPSIS
|
||||
gcloud alpha spanner instances move INSTANCE --target-config=TARGET_CONFIG
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
[--target-database-move-configs=[^:^database-id=DATABASE_ID:kms-keys=KEY1,
|
||||
KEY2,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Move the Cloud Spanner instance to the specified instance config.
|
||||
|
||||
EXAMPLES
|
||||
To move the Cloud Spanner instance to the target instance configuration,
|
||||
run: $ gcloud alpha spanner instances move my-instance-id \
|
||||
--target-config=nam3
|
||||
To move the Cloud Spanner instance, which has two CMEK 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 \
|
||||
--target-config=nam3 \
|
||||
--target-database-move-configs=^:^database-id=db1:kms-keys=proje\
|
||||
cts/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-keys=proje\
|
||||
cts/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
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
INSTANCE
|
||||
|
|
@ -22,6 +34,30 @@ REQUIRED FLAGS
|
|||
--target-config=TARGET_CONFIG
|
||||
Target Instance configuration to move the instances.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--target-database-move-configs=[^:^database-id=DATABASE_ID:kms-keys=KEY1,KEY2,...]
|
||||
Database level configurations for each database to be moved. Currently
|
||||
only used for CMEK databases to specificy the target database KMS keys.
|
||||
Sets target_database_move_configs value.
|
||||
|
||||
database-id
|
||||
Required, Sets database-id value.
|
||||
|
||||
kms-keys
|
||||
Sets kms-keys value.
|
||||
|
||||
Shorthand Example:
|
||||
|
||||
--target-database-move-configs=database-id=string,kms-keys=string --target-database-move-configs=database-id=string,kms-keys=string
|
||||
|
||||
JSON Example:
|
||||
|
||||
--target-database-move-configs='[{"database-id": "string", "kms-keys": "string"}]'
|
||||
|
||||
File Example:
|
||||
|
||||
--target-database-move-configs=path_to_file.(yaml|json)
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue