feat(spanner): update the api

#### spanner:v1

The following keys were added:
- schemas.DatabaseMoveConfig (Total Keys: 4)
- schemas.InstanceEncryptionConfig (Total Keys: 5)
- schemas.MoveInstanceRequest.properties.targetDatabaseMoveConfigs (Total Keys: 2)

The following keys were changed:
- endpoints (Total Keys: 1)

Author: yoshi-automation

docs/dyn/spanner_v1.projects.instances.databases.html

@@ -96,7 +96,7 @@ <h2>Instance Methods</h2>
 
 <p class="toc_element">
   <code><a href="#addSplitPoints">addSplitPoints(database, body=None, x__xgafv=None)</a></code></p>
-<p class="firstline">Adds split points to specified tables, indexes of a database.</p>
+<p class="firstline">Adds split points to specified tables and indexes of a database.</p>
 <p class="toc_element">
   <code><a href="#changequorum">changequorum(name, body=None, x__xgafv=None)</a></code></p>
 <p class="firstline">`ChangeQuorum` is strictly restricted to databases that use dual-region instance configurations. Initiates a background operation to change the quorum of a database from dual-region mode to single-region mode or vice versa. The returned long-running operation has a name of the format `projects//instances//databases//operations/` and can be used to track execution of the `ChangeQuorum`. The metadata field type is ChangeQuorumMetadata. Authorization requires `spanner.databases.changequorum` permission on the resource database.</p>
@@ -145,20 +145,20 @@ <h2>Instance Methods</h2>
 <h3>Method Details</h3>
 <div class="method">
     <code class="details" id="addSplitPoints">addSplitPoints(database, body=None, x__xgafv=None)</code>
-  <pre>Adds split points to specified tables, indexes of a database.
+  <pre>Adds split points to specified tables and indexes of a database.
 
 Args:
-  database: string, Required. The database on whose tables/indexes split points are to be added. Values are of the form `projects//instances//databases/`. (required)
+  database: string, Required. The database on whose tables or indexes the split points are to be added. Values are of the form `projects//instances//databases/`. (required)
   body: object, The request body.
     The object takes the form of:
 
 { # The request for AddSplitPoints.
-  &quot;initiator&quot;: &quot;A String&quot;, # Optional. A user-supplied tag associated with the split points. For example, &quot;initial_data_load&quot;, &quot;special_event_1&quot;. Defaults to &quot;CloudAddSplitPointsAPI&quot; if not specified. The length of the tag must not exceed 50 characters,else will be trimmed. Only valid UTF8 characters are allowed.
+  &quot;initiator&quot;: &quot;A String&quot;, # Optional. A user-supplied tag associated with the split points. For example, &quot;initial_data_load&quot;, &quot;special_event_1&quot;. Defaults to &quot;CloudAddSplitPointsAPI&quot; if not specified. The length of the tag must not exceed 50 characters, or else it is trimmed. Only valid UTF8 characters are allowed.
   &quot;splitPoints&quot;: [ # Required. The split points to add.
-    { # The split points of a table/index.
+    { # The split points of a table or an index.
       &quot;expireTime&quot;: &quot;A String&quot;, # Optional. The expiration timestamp of the split points. A timestamp in the past means immediate expiration. The maximum value can be 30 days in the future. Defaults to 10 days in the future if not specified.
       &quot;index&quot;: &quot;A String&quot;, # The index to split. If specified, the `table` field must refer to the index&#x27;s base table.
-      &quot;keys&quot;: [ # Required. The list of split keys, i.e., the split boundaries.
+      &quot;keys&quot;: [ # Required. The list of split keys. In essence, the split boundaries.
         { # A split key.
           &quot;keyParts&quot;: [ # Required. The column values making up the split key.
             &quot;&quot;,

docs/dyn/spanner_v1.projects.instances.databases.sessions.html

@@ -504,6 +504,17 @@ <h3>Method Details</h3>
 
 { # The request for MoveInstance.
   &quot;targetConfig&quot;: &quot;A String&quot;, # Required. The target instance configuration where to move the instance. Values are of the form `projects//instanceConfigs/`.
+  &quot;targetDatabaseMoveConfigs&quot;: [ # Optional. The configuration for each database in the target instance configuration.
+    { # The configuration for each database in the target instance configuration.
+      &quot;databaseId&quot;: &quot;A String&quot;, # Required. The unique identifier of the database resource in the Instance. For example if the database uri is projects/foo/instances/bar/databases/baz, the id to supply here is baz.
+      &quot;encryptionConfig&quot;: { # Encryption configuration for a Cloud Spanner database. # Optional. Encryption configuration to be used for the database in target configuration. Should be specified for every database which currently uses CMEK encryption. If a database currently uses GOOGLE_MANAGED encryption and a target encryption config is not specified, it defaults to GOOGLE_MANAGED. If a database currently uses Google-managed encryption and a target encryption config is specified, the request is rejected. If a database currently uses CMEK encryption, a target encryption config must be specified. You cannot move a CMEK database to a Google-managed encryption database by MoveInstance.
+        &quot;kmsKeyName&quot;: &quot;A String&quot;, # Optional. This field is maintained for backwards compatibility. For new callers, we recommend using `kms_key_names` to specify the KMS key. `kms_key_name` should only be used if the location of the KMS key matches the database instance’s configuration (location) exactly. E.g. The KMS location is in us-central1 or nam3 and the database instance is also in us-central1 or nam3. The Cloud KMS key to be used for encrypting and decrypting the database. Values are of the form `projects//locations//keyRings//cryptoKeys/`.
+        &quot;kmsKeyNames&quot;: [ # Optional. Specifies the KMS configuration for one or more keys used to encrypt the database. Values are of the form `projects//locations//keyRings//cryptoKeys/`. The keys referenced by `kms_key_names` must fully cover all regions of the database&#x27;s instance configuration. Some examples: * For regional (single-region) instance configurations, specify a regional location KMS key. * For multi-region instance configurations of type `GOOGLE_MANAGED`, either specify a multi-region location KMS key or multiple regional location KMS keys that cover all regions in the instance configuration. * For an instance configuration of type `USER_MANAGED`, specify only regional location KMS keys to cover each region in the instance configuration. Multi-region location KMS keys aren&#x27;t supported for `USER_MANAGED` type instance configurations.
+          &quot;A String&quot;,
+        ],
+      },
+    },
+  ],
 }
 
   x__xgafv: string, V1 error format.