googleapis
diff --git a/‎docs/dyn/accesscontextmanager_v1.organizations.gcpUserAccessBindings.html‎
Lines changed: 64 additions & 8 deletions b/‎docs/dyn/accesscontextmanager_v1.organizations.gcpUserAccessBindings.html‎
Lines changed: 64 additions & 8 deletions
diff --git a/‎docs/dyn/aiplatform_v1.endpoints.html‎
Lines changed: 12 additions & 9 deletions b/‎docs/dyn/aiplatform_v1.endpoints.html‎
Lines changed: 12 additions & 9 deletions
diff --git a/‎docs/dyn/aiplatform_v1.projects.locations.customJobs.html‎
Lines changed: 8 additions & 0 deletions b/‎docs/dyn/aiplatform_v1.projects.locations.customJobs.html‎
Lines changed: 8 additions & 0 deletions
@@ -213,6 +213,7 @@ <h3>Method Details</h3>
     },
   ],
   &quot;generationConfig&quot;: { # Generation config. # Optional. Generation config that the model will use to generate the response.
+    &quot;audioTimestamp&quot;: True or False, # Optional. If enabled, audio timestamp will be included in the request to the model.
     &quot;candidateCount&quot;: 42, # Optional. Number of candidates to generate.
     &quot;frequencyPenalty&quot;: 3.14, # Optional. Frequency penalties.
     &quot;logprobs&quot;: 42, # Optional. Logit probabilities.
@@ -226,7 +227,7 @@ <h3>Method Details</h3>
       ],
       &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
       &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-      &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+      &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
         &quot;A String&quot;,
       ],
       &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
@@ -318,7 +319,7 @@ <h3>Method Details</h3>
             ],
             &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
             &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-            &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+            &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
               &quot;A String&quot;,
             ],
             &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
@@ -352,7 +353,7 @@ <h3>Method Details</h3>
             ],
             &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
             &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-            &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+            &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
               &quot;A String&quot;,
             ],
             &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
@@ -472,6 +473,7 @@ <h3>Method Details</h3>
     },
   ],
   &quot;generationConfig&quot;: { # Generation config. # Optional. Generation config.
+    &quot;audioTimestamp&quot;: True or False, # Optional. If enabled, audio timestamp will be included in the request to the model.
     &quot;candidateCount&quot;: 42, # Optional. Number of candidates to generate.
     &quot;frequencyPenalty&quot;: 3.14, # Optional. Frequency penalties.
     &quot;logprobs&quot;: 42, # Optional. Logit probabilities.
@@ -485,7 +487,7 @@ <h3>Method Details</h3>
       ],
       &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
       &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-      &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+      &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
         &quot;A String&quot;,
       ],
       &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
@@ -591,7 +593,7 @@ <h3>Method Details</h3>
             ],
             &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
             &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-            &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+            &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
               &quot;A String&quot;,
             ],
             &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
@@ -625,7 +627,7 @@ <h3>Method Details</h3>
             ],
             &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
             &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-            &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+            &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
               &quot;A String&quot;,
             ],
             &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
@@ -889,6 +891,7 @@ <h3>Method Details</h3>
     },
   ],
   &quot;generationConfig&quot;: { # Generation config. # Optional. Generation config.
+    &quot;audioTimestamp&quot;: True or False, # Optional. If enabled, audio timestamp will be included in the request to the model.
     &quot;candidateCount&quot;: 42, # Optional. Number of candidates to generate.
     &quot;frequencyPenalty&quot;: 3.14, # Optional. Frequency penalties.
     &quot;logprobs&quot;: 42, # Optional. Logit probabilities.
@@ -902,7 +905,7 @@ <h3>Method Details</h3>
       ],
       &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
       &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-      &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+      &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
         &quot;A String&quot;,
       ],
       &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
@@ -1008,7 +1011,7 @@ <h3>Method Details</h3>
             ],
             &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
             &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-            &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+            &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
               &quot;A String&quot;,
             ],
             &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
@@ -1042,7 +1045,7 @@ <h3>Method Details</h3>
             ],
             &quot;default&quot;: &quot;&quot;, # Optional. Default value of the data.
             &quot;description&quot;: &quot;A String&quot;, # Optional. The description of the data.
-            &quot;enum&quot;: [ # Optional. Possible values of the element of Type.STRING with enum format. For example we can define an Enum Direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]}
+            &quot;enum&quot;: [ # Optional. Possible values of the element of primitive type with enum format. Examples: 1. We can define direction as : {type:STRING, format:enum, enum:[&quot;EAST&quot;, NORTH&quot;, &quot;SOUTH&quot;, &quot;WEST&quot;]} 2. We can define apartment number as : {type:INTEGER, format:enum, enum:[&quot;101&quot;, &quot;201&quot;, &quot;301&quot;]}
               &quot;A String&quot;,
             ],
             &quot;example&quot;: &quot;&quot;, # Optional. Example of the object. Will only populated when the object is the root.
 
@@ -169,6 +169,8 @@ <h3>Method Details</h3>
     &quot;network&quot;: &quot;A String&quot;, # Optional. The full name of the Compute Engine [network](/compute/docs/networks-and-firewalls#networks) to which the Job should be peered. For example, `projects/12345/global/networks/myVPC`. [Format](/compute/docs/reference/rest/v1/networks/insert) is of the form `projects/{project}/global/networks/{network}`. Where {project} is a project number, as in `12345`, and {network} is a network name. To specify this field, you must have already [configured VPC Network Peering for Vertex AI](https://cloud.google.com/vertex-ai/docs/general/vpc-peering). If this field is left unspecified, the job is not peered with any network.
     &quot;persistentResourceId&quot;: &quot;A String&quot;, # Optional. The ID of the PersistentResource in the same Project and Location which to run If this is specified, the job will be run on existing machines held by the PersistentResource instead of on-demand short-live machines. The network and CMEK configs on the job should be consistent with those on the PersistentResource, otherwise, the job will be rejected.
     &quot;protectedArtifactLocationId&quot;: &quot;A String&quot;, # The ID of the location to store protected artifacts. e.g. us-central1. Populate only when the location is different than CustomJob location. List of supported locations: https://cloud.google.com/vertex-ai/docs/general/locations
+    &quot;pscInterfaceConfig&quot;: { # Configuration for PSC-I. # Optional. Configuration for PSC-I for CustomJob.
+    },
     &quot;reservedIpRanges&quot;: [ # Optional. A list of names for the reserved ip ranges under the VPC network that can be used for this job. If set, we will deploy the job within the provided ip ranges. Otherwise, the job will be deployed to any ip ranges under the provided VPC network. Example: [&#x27;vertex-ai-ip-range&#x27;].
       &quot;A String&quot;,
     ],
@@ -294,6 +296,8 @@ <h3>Method Details</h3>
     &quot;network&quot;: &quot;A String&quot;, # Optional. The full name of the Compute Engine [network](/compute/docs/networks-and-firewalls#networks) to which the Job should be peered. For example, `projects/12345/global/networks/myVPC`. [Format](/compute/docs/reference/rest/v1/networks/insert) is of the form `projects/{project}/global/networks/{network}`. Where {project} is a project number, as in `12345`, and {network} is a network name. To specify this field, you must have already [configured VPC Network Peering for Vertex AI](https://cloud.google.com/vertex-ai/docs/general/vpc-peering). If this field is left unspecified, the job is not peered with any network.
     &quot;persistentResourceId&quot;: &quot;A String&quot;, # Optional. The ID of the PersistentResource in the same Project and Location which to run If this is specified, the job will be run on existing machines held by the PersistentResource instead of on-demand short-live machines. The network and CMEK configs on the job should be consistent with those on the PersistentResource, otherwise, the job will be rejected.
     &quot;protectedArtifactLocationId&quot;: &quot;A String&quot;, # The ID of the location to store protected artifacts. e.g. us-central1. Populate only when the location is different than CustomJob location. List of supported locations: https://cloud.google.com/vertex-ai/docs/general/locations
+    &quot;pscInterfaceConfig&quot;: { # Configuration for PSC-I. # Optional. Configuration for PSC-I for CustomJob.
+    },
     &quot;reservedIpRanges&quot;: [ # Optional. A list of names for the reserved ip ranges under the VPC network that can be used for this job. If set, we will deploy the job within the provided ip ranges. Otherwise, the job will be deployed to any ip ranges under the provided VPC network. Example: [&#x27;vertex-ai-ip-range&#x27;].
       &quot;A String&quot;,
     ],
@@ -461,6 +465,8 @@ <h3>Method Details</h3>
     &quot;network&quot;: &quot;A String&quot;, # Optional. The full name of the Compute Engine [network](/compute/docs/networks-and-firewalls#networks) to which the Job should be peered. For example, `projects/12345/global/networks/myVPC`. [Format](/compute/docs/reference/rest/v1/networks/insert) is of the form `projects/{project}/global/networks/{network}`. Where {project} is a project number, as in `12345`, and {network} is a network name. To specify this field, you must have already [configured VPC Network Peering for Vertex AI](https://cloud.google.com/vertex-ai/docs/general/vpc-peering). If this field is left unspecified, the job is not peered with any network.
     &quot;persistentResourceId&quot;: &quot;A String&quot;, # Optional. The ID of the PersistentResource in the same Project and Location which to run If this is specified, the job will be run on existing machines held by the PersistentResource instead of on-demand short-live machines. The network and CMEK configs on the job should be consistent with those on the PersistentResource, otherwise, the job will be rejected.
     &quot;protectedArtifactLocationId&quot;: &quot;A String&quot;, # The ID of the location to store protected artifacts. e.g. us-central1. Populate only when the location is different than CustomJob location. List of supported locations: https://cloud.google.com/vertex-ai/docs/general/locations
+    &quot;pscInterfaceConfig&quot;: { # Configuration for PSC-I. # Optional. Configuration for PSC-I for CustomJob.
+    },
     &quot;reservedIpRanges&quot;: [ # Optional. A list of names for the reserved ip ranges under the VPC network that can be used for this job. If set, we will deploy the job within the provided ip ranges. Otherwise, the job will be deployed to any ip ranges under the provided VPC network. Example: [&#x27;vertex-ai-ip-range&#x27;].
       &quot;A String&quot;,
     ],
@@ -599,6 +605,8 @@ <h3>Method Details</h3>
         &quot;network&quot;: &quot;A String&quot;, # Optional. The full name of the Compute Engine [network](/compute/docs/networks-and-firewalls#networks) to which the Job should be peered. For example, `projects/12345/global/networks/myVPC`. [Format](/compute/docs/reference/rest/v1/networks/insert) is of the form `projects/{project}/global/networks/{network}`. Where {project} is a project number, as in `12345`, and {network} is a network name. To specify this field, you must have already [configured VPC Network Peering for Vertex AI](https://cloud.google.com/vertex-ai/docs/general/vpc-peering). If this field is left unspecified, the job is not peered with any network.
         &quot;persistentResourceId&quot;: &quot;A String&quot;, # Optional. The ID of the PersistentResource in the same Project and Location which to run If this is specified, the job will be run on existing machines held by the PersistentResource instead of on-demand short-live machines. The network and CMEK configs on the job should be consistent with those on the PersistentResource, otherwise, the job will be rejected.
         &quot;protectedArtifactLocationId&quot;: &quot;A String&quot;, # The ID of the location to store protected artifacts. e.g. us-central1. Populate only when the location is different than CustomJob location. List of supported locations: https://cloud.google.com/vertex-ai/docs/general/locations
+        &quot;pscInterfaceConfig&quot;: { # Configuration for PSC-I. # Optional. Configuration for PSC-I for CustomJob.
+        },
         &quot;reservedIpRanges&quot;: [ # Optional. A list of names for the reserved ip ranges under the VPC network that can be used for this job. If set, we will deploy the job within the provided ip ranges. Otherwise, the job will be deployed to any ip ranges under the provided VPC network. Example: [&#x27;vertex-ai-ip-range&#x27;].
           &quot;A String&quot;,
         ],