imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 06:47:12 +00:00
Code Activity

gcloud: Wed Feb 12 10:41:39 UTC 2025

Browse source
This commit is contained in:
Automated 2025-02-12 10:41:39 +00:00
parent c854ee0644
commit 44f319c56c
119 changed files with 5956 additions and 337 deletions
Download patch file Download diff file Expand all files Collapse all files

3
gcloud/spanner/instances/help
View file

@ -37,7 +37,8 @@ COMMANDS
List the Cloud Spanner instances in this project.
move
Move the Cloud Spanner instance to the specified instance config.
Move the Cloud Spanner instance to the specified instance
configuration.
remove-iam-policy-binding
Remove IAM policy binding of a Cloud Spanner instance.

47
gcloud/spanner/instances/move
View file

@ -1,17 +1,30 @@
NAME
gcloud spanner instances move - move the Cloud Spanner instance to the
specified instance config
specified instance configuration
SYNOPSIS
gcloud spanner instances move INSTANCE --target-config=TARGET_CONFIG
[GCLOUD_WIDE_FLAG ...]
[--target-database-move-configs=[^:^database-id=DATABASE_ID:kms-key-names=KEY1,
KEY2,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Move the Cloud Spanner instance to the specified instance config.
Move the Cloud Spanner instance to the specified instance configuration.
EXAMPLES
To move the Cloud Spanner instance to the target instance configuration,
run: $ gcloud spanner instances move my-instance-id --target-config=nam3
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 spanner instances move my-instance-id \
--target-config=nam3 \
--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
POSITIONAL ARGUMENTS
INSTANCE
@ -21,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-key-names=KEY1,KEY2,...]
Database level configurations for each database to be moved. Currently
only used for CMEK-enabled databases to specificy the target database
KMS keys. Sets target_database_move_configs value.
database-id
Required, Sets database-id value.
kms-key-names
Sets kms-key-names value.
Shorthand Example:
--target-database-move-configs=database-id=string,kms-key-names=string --target-database-move-configs=database-id=string,kms-key-names=string
JSON Example:
--target-database-move-configs='[{"database-id": "string", "kms-key-names": "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,