googleapis
diff --git a/‎docs/dyn/admin_directory_v1.groups.html‎
Lines changed: 1 addition & 1 deletion b/‎docs/dyn/admin_directory_v1.groups.html‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/dyn/admin_directory_v1.resources.calendars.html‎
Lines changed: 1 addition & 1 deletion b/‎docs/dyn/admin_directory_v1.resources.calendars.html‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/dyn/admin_directory_v1.users.html‎
Lines changed: 1 addition & 1 deletion b/‎docs/dyn/admin_directory_v1.users.html‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/dyn/adsense_v2.accounts.reports.html‎
Lines changed: 4 additions & 0 deletions b/‎docs/dyn/adsense_v2.accounts.reports.html‎
Lines changed: 4 additions & 0 deletions
diff --git a/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.artifacts.html‎
Lines changed: 1 addition & 1 deletion b/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.artifacts.html‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.contexts.html‎
Lines changed: 1 addition & 1 deletion b/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.contexts.html‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.executions.html‎
Lines changed: 1 addition & 1 deletion b/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.executions.html‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.html‎
Lines changed: 1 addition & 1 deletion b/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.html‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.metadataSchemas.html‎
Lines changed: 1 addition & 1 deletion b/‎docs/dyn/aiplatform_v1.projects.locations.metadataStores.metadataSchemas.html‎
Lines changed: 1 addition & 1 deletion
@@ -217,7 +217,7 @@ <h3>Method Details</h3>
     Allowed values
       email - Email of the group.
   pageToken: string, Token to specify next page in the list
-  query: string, Query string search. Should be of the form &quot;&quot;. Complete documentation is at https://developers.google.com/workspace/admin/directory/v1/guides/search-groups
+  query: string, Query string search. Contains one or more search clauses, each with a field, operator, and value. For complete documentation, go to [Search for groups](https://developers.google.com/workspace/admin/directory/v1/guides/search-groups).
   sortOrder: string, Whether to return results in ascending or descending order. Only of use when orderBy is also used
     Allowed values
       ASCENDING - Ascending order.
 
@@ -215,7 +215,7 @@ <h3>Method Details</h3>
   maxResults: integer, Maximum number of results to return.
   orderBy: string, Field(s) to sort results by in either ascending or descending order. Supported fields include `resourceId`, `resourceName`, `capacity`, `buildingId`, and `floorName`. If no order is specified, defaults to ascending. Should be of the form &quot;field [asc|desc], field [asc|desc], ...&quot;. For example `buildingId, capacity desc` would return results sorted first by `buildingId` in ascending order then by `capacity` in descending order.
   pageToken: string, Token to specify the next page in the list.
-  query: string, String query used to filter results. Should be of the form &quot;field operator value&quot; where field can be any of supported fields and operators can be any of supported operations. Operators include &#x27;=&#x27; for exact match, &#x27;!=&#x27; for mismatch and &#x27;:&#x27; for prefix match or HAS match where applicable. For prefix match, the value should always be followed by a *. Logical operators NOT and AND are supported (in this order of precedence). Supported fields include `generatedResourceName`, `name`, `buildingId`, `floor_name`, `capacity`, `featureInstances.feature.name`, `resourceEmail`, `resourceCategory`. For example `buildingId=US-NYC-9TH AND featureInstances.feature.name:Phone`.
+  query: string, String query used to filter results. Contains one or more search clauses, each with a field, operator, and value. A field can be any of supported fields and operators can be any of supported operations. Operators include &#x27;=&#x27; for exact match, &#x27;!=&#x27; for mismatch and &#x27;:&#x27; for prefix match or HAS match where applicable. For prefix match, the value should always be followed by a *. Logical operators NOT and AND are supported (in this order of precedence). Supported fields include `generatedResourceName`, `name`, `buildingId`, `floor_name`, `capacity`, `featureInstances.feature.name`, `resourceEmail`, `resourceCategory`. For example `buildingId=US-NYC-9TH AND featureInstances.feature.name:Phone`.
   x__xgafv: string, V1 error format.
     Allowed values
       1 - v1 error format
 
@@ -880,7 +880,7 @@ <h3>Method Details</h3>
       basic - Do not include any custom fields for the user.
       custom - Include custom fields from schemas mentioned in customFieldMask.
       full - Include all fields associated with this user.
-  query: string, Query string search. Should be of the form &quot;&quot;. Complete documentation is at https://developers.google.com/workspace/admin/directory/v1/guides/search-users
+  query: string, Query string search. Contains one or more search clauses, each with a field, operator, and value. For complete documentation, go to [Search for users](https://developers.google.com/workspace/admin/directory/v1/guides/search-users).
   showDeleted: string, If set to true, retrieves the list of deleted users. (Default: false)
   sortOrder: string, Whether to return results in ascending or descending order.
     Allowed values
 
@@ -151,6 +151,8 @@ <h3>Method Details</h3>
       PLATFORM_TYPE_CODE - Platform type code (e.g. &quot;HighEndMobile&quot;, &quot;Desktop&quot;).
       TARGETING_TYPE_NAME - Localized targeting type name (e.g. &quot;Contextual&quot;, &quot;Personalized&quot;, &quot;Run of Network&quot;).
       TARGETING_TYPE_CODE - Targeting type code (e.g. &quot;Keyword&quot;, &quot;UserInterest&quot;, &quot;RunOfNetwork&quot;).
+      TRAFFIC_SOURCE_NAME - Localized traffic source name (e.g. &quot;Google&quot;, &quot;Bing&quot;, &quot;Facebook&quot;, &quot;Other&quot;). For more information, see [Traffic source breakdown](https://support.google.com/adsense/answer/16474600).
+      TRAFFIC_SOURCE_CODE - Traffic source code (e.g. &quot;GOOGLE&quot;, &quot;BING&quot;, &quot;FACEBOOK&quot;, &quot;OTHER&quot;). For more information, see [Traffic source breakdown](https://support.google.com/adsense/answer/16474600).
       CONTENT_PLATFORM_NAME - Localized content platform name an ad request was made from (e.g. &quot;AMP&quot;, &quot;Web&quot;).
       CONTENT_PLATFORM_CODE - Content platform code an ad request was made from (e.g. &quot;AMP&quot;, &quot;HTML&quot;).
       AD_PLACEMENT_NAME - Localized ad placement name (e.g. &quot;Ad unit&quot;, &quot;Global settings&quot;, &quot;Manual&quot;).
@@ -329,6 +331,8 @@ <h3>Method Details</h3>
       PLATFORM_TYPE_CODE - Platform type code (e.g. &quot;HighEndMobile&quot;, &quot;Desktop&quot;).
       TARGETING_TYPE_NAME - Localized targeting type name (e.g. &quot;Contextual&quot;, &quot;Personalized&quot;, &quot;Run of Network&quot;).
       TARGETING_TYPE_CODE - Targeting type code (e.g. &quot;Keyword&quot;, &quot;UserInterest&quot;, &quot;RunOfNetwork&quot;).
+      TRAFFIC_SOURCE_NAME - Localized traffic source name (e.g. &quot;Google&quot;, &quot;Bing&quot;, &quot;Facebook&quot;, &quot;Other&quot;). For more information, see [Traffic source breakdown](https://support.google.com/adsense/answer/16474600).
+      TRAFFIC_SOURCE_CODE - Traffic source code (e.g. &quot;GOOGLE&quot;, &quot;BING&quot;, &quot;FACEBOOK&quot;, &quot;OTHER&quot;). For more information, see [Traffic source breakdown](https://support.google.com/adsense/answer/16474600).
       CONTENT_PLATFORM_NAME - Localized content platform name an ad request was made from (e.g. &quot;AMP&quot;, &quot;Web&quot;).
       CONTENT_PLATFORM_CODE - Content platform code an ad request was made from (e.g. &quot;AMP&quot;, &quot;HTML&quot;).
       AD_PLACEMENT_NAME - Localized ad placement name (e.g. &quot;Ad unit&quot;, &quot;Global settings&quot;, &quot;Manual&quot;).
 
@@ -247,7 +247,7 @@ <h3>Method Details</h3>
   parent: string, Required. The MetadataStore whose Artifacts should be listed. Format: `projects/{project}/locations/{location}/metadataStores/{metadatastore}` (required)
   filter: string, Filter specifying the boolean condition for the Artifacts to satisfy in order to be part of the result set. The syntax to define filter query is based on https://google.aip.dev/160. The supported set of filters include the following: * **Attribute filtering**: For example: `display_name = &quot;test&quot;`. Supported fields include: `name`, `display_name`, `uri`, `state`, `schema_title`, `create_time`, and `update_time`. Time fields, such as `create_time` and `update_time`, require values specified in RFC-3339 format. For example: `create_time = &quot;2020-11-19T11:30:00-04:00&quot;` * **Metadata field**: To filter on metadata fields use traversal operation as follows: `metadata..`. For example: `metadata.field_1.number_value = 10.0` In case the field name contains special characters (such as colon), one can embed it inside double quote. For example: `metadata.&quot;field:1&quot;.number_value = 10.0` * **Context based filtering**: To filter Artifacts based on the contexts to which they belong, use the function operator with the full resource name `in_context()`. For example: `in_context(&quot;projects//locations//metadataStores//contexts/&quot;)` Each of the above supported filter types can be combined together using logical operators (`AND` &amp; `OR`). Maximum nested expression depth allowed is 5. For example: `display_name = &quot;test&quot; AND metadata.field1.bool_value = true`.
   orderBy: string, How the list of messages is ordered. Specify the values to order by and an ordering operation. The default sorting order is ascending. To specify descending order for a field, users append a &quot; desc&quot; suffix; for example: &quot;foo desc, bar&quot;. Subfields are specified with a `.` character, such as foo.bar. see https://google.aip.dev/132#ordering for more details.
-  pageSize: integer, The maximum number of Artifacts to return. The service may return fewer. Must be in range 1-1000, inclusive. Defaults to 100.
+  pageSize: integer, The maximum number of Artifacts to return. The service may return fewer. Must be in range 1-100, inclusive. Defaults to 100.
   pageToken: string, A page token, received from a previous MetadataService.ListArtifacts call. Provide this to retrieve the subsequent page. When paginating, all other provided parameters must match the call that provided the page token. (Otherwise the request will fail with INVALID_ARGUMENT error.)
   x__xgafv: string, V1 error format.
     Allowed values
 
@@ -317,7 +317,7 @@ <h3>Method Details</h3>
   parent: string, Required. The MetadataStore whose Contexts should be listed. Format: `projects/{project}/locations/{location}/metadataStores/{metadatastore}` (required)
   filter: string, Filter specifying the boolean condition for the Contexts to satisfy in order to be part of the result set. The syntax to define filter query is based on https://google.aip.dev/160. Following are the supported set of filters: * **Attribute filtering**: For example: `display_name = &quot;test&quot;`. Supported fields include: `name`, `display_name`, `schema_title`, `create_time`, and `update_time`. Time fields, such as `create_time` and `update_time`, require values specified in RFC-3339 format. For example: `create_time = &quot;2020-11-19T11:30:00-04:00&quot;`. * **Metadata field**: To filter on metadata fields use traversal operation as follows: `metadata..`. For example: `metadata.field_1.number_value = 10.0`. In case the field name contains special characters (such as colon), one can embed it inside double quote. For example: `metadata.&quot;field:1&quot;.number_value = 10.0` * **Parent Child filtering**: To filter Contexts based on parent-child relationship use the HAS operator as follows: ``` parent_contexts: &quot;projects//locations//metadataStores//contexts/&quot; child_contexts: &quot;projects//locations//metadataStores//contexts/&quot; ``` Each of the above supported filters can be combined together using logical operators (`AND` &amp; `OR`). Maximum nested expression depth allowed is 5. For example: `display_name = &quot;test&quot; AND metadata.field1.bool_value = true`.
   orderBy: string, How the list of messages is ordered. Specify the values to order by and an ordering operation. The default sorting order is ascending. To specify descending order for a field, users append a &quot; desc&quot; suffix; for example: &quot;foo desc, bar&quot;. Subfields are specified with a `.` character, such as foo.bar. see https://google.aip.dev/132#ordering for more details.
-  pageSize: integer, The maximum number of Contexts to return. The service may return fewer. Must be in range 1-1000, inclusive. Defaults to 100.
+  pageSize: integer, The maximum number of Contexts to return. The service may return fewer. Must be in range 1-100, inclusive. Defaults to 100.
   pageToken: string, A page token, received from a previous MetadataService.ListContexts call. Provide this to retrieve the subsequent page. When paginating, all other provided parameters must match the call that provided the page token. (Otherwise the request will fail with INVALID_ARGUMENT error.)
   x__xgafv: string, V1 error format.
     Allowed values
 
@@ -282,7 +282,7 @@ <h3>Method Details</h3>
   parent: string, Required. The MetadataStore whose Executions should be listed. Format: `projects/{project}/locations/{location}/metadataStores/{metadatastore}` (required)
   filter: string, Filter specifying the boolean condition for the Executions to satisfy in order to be part of the result set. The syntax to define filter query is based on https://google.aip.dev/160. Following are the supported set of filters: * **Attribute filtering**: For example: `display_name = &quot;test&quot;`. Supported fields include: `name`, `display_name`, `state`, `schema_title`, `create_time`, and `update_time`. Time fields, such as `create_time` and `update_time`, require values specified in RFC-3339 format. For example: `create_time = &quot;2020-11-19T11:30:00-04:00&quot;`. * **Metadata field**: To filter on metadata fields use traversal operation as follows: `metadata..` For example: `metadata.field_1.number_value = 10.0` In case the field name contains special characters (such as colon), one can embed it inside double quote. For example: `metadata.&quot;field:1&quot;.number_value = 10.0` * **Context based filtering**: To filter Executions based on the contexts to which they belong use the function operator with the full resource name: `in_context()`. For example: `in_context(&quot;projects//locations//metadataStores//contexts/&quot;)` Each of the above supported filters can be combined together using logical operators (`AND` &amp; `OR`). Maximum nested expression depth allowed is 5. For example: `display_name = &quot;test&quot; AND metadata.field1.bool_value = true`.
   orderBy: string, How the list of messages is ordered. Specify the values to order by and an ordering operation. The default sorting order is ascending. To specify descending order for a field, users append a &quot; desc&quot; suffix; for example: &quot;foo desc, bar&quot;. Subfields are specified with a `.` character, such as foo.bar. see https://google.aip.dev/132#ordering for more details.
-  pageSize: integer, The maximum number of Executions to return. The service may return fewer. Must be in range 1-1000, inclusive. Defaults to 100.
+  pageSize: integer, The maximum number of Executions to return. The service may return fewer. Must be in range 1-100, inclusive. Defaults to 100.
   pageToken: string, A page token, received from a previous MetadataService.ListExecutions call. Provide this to retrieve the subsequent page. When paginating, all other provided parameters must match the call that provided the page token. (Otherwise the request will fail with an INVALID_ARGUMENT error.)
   x__xgafv: string, V1 error format.
     Allowed values
 
@@ -251,7 +251,7 @@ <h3>Method Details</h3>
 
 Args:
   parent: string, Required. The Location whose MetadataStores should be listed. Format: `projects/{project}/locations/{location}` (required)
-  pageSize: integer, The maximum number of Metadata Stores to return. The service may return fewer. Must be in range 1-1000, inclusive. Defaults to 100.
+  pageSize: integer, The maximum number of Metadata Stores to return. The service may return fewer. Must be in range 1-100, inclusive. Defaults to 100.
   pageToken: string, A page token, received from a previous MetadataService.ListMetadataStores call. Provide this to retrieve the subsequent page. When paginating, all other provided parameters must match the call that provided the page token. (Otherwise the request will fail with INVALID_ARGUMENT error.)
   x__xgafv: string, V1 error format.
     Allowed values
 
@@ -163,7 +163,7 @@ <h3>Method Details</h3>
 Args:
   parent: string, Required. The MetadataStore whose MetadataSchemas should be listed. Format: `projects/{project}/locations/{location}/metadataStores/{metadatastore}` (required)
   filter: string, A query to filter available MetadataSchemas for matching results.
-  pageSize: integer, The maximum number of MetadataSchemas to return. The service may return fewer. Must be in range 1-1000, inclusive. Defaults to 100.
+  pageSize: integer, The maximum number of MetadataSchemas to return. The service may return fewer. Must be in range 1-100, inclusive. Defaults to 100.
   pageToken: string, A page token, received from a previous MetadataService.ListMetadataSchemas call. Provide this to retrieve the next page. When paginating, all other provided parameters must match the call that provided the page token. (Otherwise the request will fail with INVALID_ARGUMENT error.)
   x__xgafv: string, V1 error format.
     Allowed values