.TH "GCLOUD_ALPHA_SPANNER_INSTANCES_MOVE" 1



.SH "NAME"
.HP
gcloud alpha spanner instances move \- move the Cloud Spanner instance to the specified instance configuration



.SH "SYNOPSIS"
.HP
\f5gcloud alpha spanner instances move\fR \fIINSTANCE\fR \fB\-\-target\-config\fR=\fITARGET_CONFIG\fR [\fB\-\-target\-database\-move\-configs\fR=[^:^\fIdatabase\-id\fR=\fIDATABASE_ID\fR:\fIkms\-key\-names\fR=\fIKEY1\fR,\fIKEY2\fR,...]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Move the Cloud Spanner instance to the specified instance
configuration.



.SH "EXAMPLES"

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:.RS 2m
$ gcloud alpha spanner instances move my\-instance\-id \e
    \-\-target\-config=nam3 \e
    \-\-target\-database\-move\-configs=^:^database\-id=db1:kms\-key\-names=\e
projects/myproject/locations/us\-east4/keyRings/mykeyring/\e
cryptoKeys/cmek\-key,projects/myproject/locations/us\-east1/keyRings/\e
mykeyring/cryptoKeys/cmek\-key,projects/myproject/locations/\e
us\-central1/keyRings/mykeyring/cryptoKeys/cmek\-key \e
    \-\-target\-database\-move\-configs=^:^database\-id=db2:kms\-key\-names=\e
projects/myproject/locations/us\-east4/keyRings/mykeyring/\e
cryptoKeys/cmek\-key,projects/myproject/locations/us\-east1/keyRings/\e
mykeyring/cryptoKeys/cmek\-key,projects/myproject/locations/\e
us\-central1/keyRings/mykeyring/cryptoKeys/cmek\-key

.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIINSTANCE\fR

Cloud Spanner instance ID.


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-target\-config\fR=\fITARGET_CONFIG\fR

Target Instance configuration to move the instances.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-target\-database\-move\-configs\fR=[^:^\fIdatabase\-id\fR=\fIDATABASE_ID\fR:\fIkms\-key\-names\fR=\fIKEY1\fR,\fIKEY2\fR,...]

Database level configurations for each database to be moved. Currently only used
for CMEK\-enabled databases to specificy the target database KMS keys. Sets
\f5target_database_move_configs\fR value.

.RS 2m
.TP 2m
\fBdatabase\-id\fR
Required, sets \f5database\-id\fR value.

.TP 2m
\fBkms\-key\-names\fR
Sets \f5kms\-key\-names\fR value.

.RE
.sp
\fBShorthand Example:\fR


.RS 2m
\-\-target\-database\-move\-configs=database\-id=string,kms\-key\-names=string \-\-target\-database\-move\-configs=database\-id=string,kms\-key\-names=string
.RE


\fBJSON Example:\fR


.RS 2m
\-\-target\-database\-move\-configs='[{"database\-id": "string", "kms\-key\-names": "string"}]'
.RE


\fBFile Example:\fR


.RS 2m
\-\-target\-database\-move\-configs=path_to_file.(yaml|json)
.RE



.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "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:

.RS 2m
$ gcloud spanner instances move
.RE

.RS 2m
$ gcloud beta spanner instances move
.RE