feat: Automated regeneration of AlloyDB client (#12473)

Auto-created at 2024-11-03 13:15:12 +0000 using the toys pull request generator.

clients/alloy_db/lib/google_api/alloy_db/v1/metadata.ex

@@ -20,7 +20,7 @@ defmodule GoogleApi.AlloyDB.V1 do
   API client metadata for GoogleApi.AlloyDB.V1.
   """
 
-  @discovery_revision "20241015"
+  @discovery_revision "20241023"
 
   def discovery_revision(), do: @discovery_revision
 end

clients/alloy_db/lib/google_api/alloy_db/v1/model/instance.ex

@@ -25,7 +25,7 @@ defmodule GoogleApi.AlloyDB.V1.Model.Instance do
   *   `availabilityType` (*type:* `String.t`, *default:* `nil`) - Availability type of an Instance. If empty, defaults to REGIONAL for primary instances. For read pools, availability_type is always UNSPECIFIED. Instances in the read pools are evenly distributed across available zones within the region (i.e. read pools with more than one node will have a node in at least two zones).
   *   `clientConnectionConfig` (*type:* `GoogleApi.AlloyDB.V1.Model.ClientConnectionConfig.t`, *default:* `nil`) - Optional. Client connection specific configurations
   *   `createTime` (*type:* `DateTime.t`, *default:* `nil`) - Output only. Create time stamp
-  *   `databaseFlags` (*type:* `map()`, *default:* `nil`) - Database flags. Set at instance level. * They are copied from primary instance on read instance creation. * Read instances can set new or override existing flags that are relevant for reads, e.g. for enabling columnar cache on a read instance. Flags set on read instance may or may not be present on primary. This is a list of "key": "value" pairs. "key": The name of the flag. These flags are passed at instance setup time, so include both server options and system variables for Postgres. Flags are specified with underscores, not hyphens. "value": The value of the flag. Booleans are set to **on** for true and **off** for false. This field must be omitted if the flag doesn't take a value.
+  *   `databaseFlags` (*type:* `map()`, *default:* `nil`) - Database flags. Set at the instance level. They are copied from the primary instance on secondary instance creation. Flags that have restrictions default to the value at primary instance on read instances during creation. Read instances can set new flags or override existing flags that are relevant for reads, for example, for enabling columnar cache on a read instance. Flags set on read instance might or might not be present on the primary instance. This is a list of "key": "value" pairs. "key": The name of the flag. These flags are passed at instance setup time, so include both server options and system variables for Postgres. Flags are specified with underscores, not hyphens. "value": The value of the flag. Booleans are set to **on** for true and **off** for false. This field must be omitted if the flag doesn't take a value.
   *   `deleteTime` (*type:* `DateTime.t`, *default:* `nil`) - Output only. Delete time stamp
   *   `displayName` (*type:* `String.t`, *default:* `nil`) - User-settable and human-readable display name for the Instance.
   *   `etag` (*type:* `String.t`, *default:* `nil`) - For Resource freshness validation (https://google.aip.dev/154)

clients/alloy_db/mix.exs

@@ -18,7 +18,7 @@
 defmodule GoogleApi.AlloyDB.Mixfile do
   use Mix.Project
 
-  @version "0.13.0"
+  @version "0.13.1"
 
   def project() do
     [