@googleapis/discoveryengine 37.1.0 → 37.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/build/v1beta.d.ts CHANGED
@@ -1393,6 +1393,12 @@ export declare namespace discoveryengine_v1beta {
1393
1393
  * Reasons for not answering the assist call.
1394
1394
  */
1395
1395
  assistSkippedReasons?: string[] | null;
1396
+ /**
1397
+ * Output only. Maps an internal connector agent name (the machine identifier embedded in tool names, e.g. `custom_mcp__agent`) to the connector's human-readable display name. Populated at serving time for custom MCP / agent gateway connectors so user-facing surfaces (e.g. the tool-call chip) can show the connector name instead of its internal identifier. Empty when there are no such connectors.
1398
+ */
1399
+ connectorDisplayNames?: {
1400
+ [key: string]: string;
1401
+ } | null;
1396
1402
  /**
1397
1403
  * Optional. The field contains information about the various policy checks' results like the banned phrases or the Model Armor checks. This field is populated only if the assist call was skipped due to a policy violation.
1398
1404
  */
@@ -2472,7 +2478,7 @@ export declare namespace discoveryengine_v1beta {
2472
2478
  */
2473
2479
  syncMode?: string | null;
2474
2480
  /**
2475
- * Optional. Immutable. User-facing, version-independent label for this connector. May be shared by multiple connectors under the same (project, location, collection, data_source); tag-based lookup returns the one with the greatest create_time. Optional at Create time. Agent Designer resolves connectors via (data_source, tag) when set, falling back to the legacy resource-name lookup when unset, so connectors created before the tag-write launch continue to work without a backfill.
2481
+ * Optional. Immutable. User-facing, version-independent label for this connector. May be shared by multiple connectors under the same (project, location, collection, data_source); tag-based lookup returns the one with the greatest create_time. Optional at Create time. If the caller omits `tag`, the server auto-derives one from the collection_id (falling back to data_source, else a time-based `t-` sentinel). The auto-derived tag is subject to the same immutability guarantee as a caller-supplied one, so callers who care about the exact tag value should provide it explicitly rather than relying on the server default. Agent Designer resolves connectors via (data_source, tag) when set, falling back to the legacy resource-name lookup when unset, so connectors created before the tag-write launch continue to work without a backfill.
2476
2482
  */
2477
2483
  tag?: string | null;
2478
2484
  /**
@@ -4114,6 +4120,10 @@ export declare namespace discoveryengine_v1beta {
4114
4120
  * Optional. Whether the license config should be auto renewed when it reaches the end date.
4115
4121
  */
4116
4122
  autoRenew?: boolean | null;
4123
+ /**
4124
+ * Output only. The name of the BillingAccountLicenseConfig from which this LicenseConfig is assigned, if this field is set.
4125
+ */
4126
+ billingAccountLicenseConfig?: string | null;
4117
4127
  /**
4118
4128
  * Output only. Indication of whether the subscription is terminated earlier than the expiration date. This is usually terminated by pipeline once the subscription gets terminated from subsv3.
4119
4129
  */
@@ -7705,6 +7715,12 @@ export declare namespace discoveryengine_v1beta {
7705
7715
  * Reasons for not answering the assist call.
7706
7716
  */
7707
7717
  assistSkippedReasons?: string[] | null;
7718
+ /**
7719
+ * Output only. Maps an internal connector agent name (the machine identifier embedded in tool names, e.g. `custom_mcp__agent`) to the connector's human-readable display name. Populated at serving time for custom MCP / agent gateway connectors so user-facing surfaces (e.g. the tool-call chip) can show the connector name instead of its internal identifier. Empty when there are no such connectors.
7720
+ */
7721
+ connectorDisplayNames?: {
7722
+ [key: string]: string;
7723
+ } | null;
7708
7724
  /**
7709
7725
  * Optional. The field contains information about the various policy checks' results like the banned phrases or the Model Armor checks. This field is populated only if the assist call was skipped due to a policy violation.
7710
7726
  */
@@ -8762,7 +8778,7 @@ export declare namespace discoveryengine_v1beta {
8762
8778
  */
8763
8779
  selectedPosition?: number | null;
8764
8780
  /**
8765
- * End user selected CompleteQueryResponse.QuerySuggestion.suggestion.
8781
+ * Optional. End user selected CompleteQueryResponse.QuerySuggestion.suggestion.
8766
8782
  */
8767
8783
  selectedSuggestion?: string | null;
8768
8784
  }
@@ -10422,6 +10438,10 @@ export declare namespace discoveryengine_v1beta {
10422
10438
  * Name of the newly generated or continued session.
10423
10439
  */
10424
10440
  session?: string | null;
10441
+ /**
10442
+ * Optional. The full resource name of the Sobi task if the conversation was handled by a long-running agent task. Format: projects/{project\}/locations/{location\}/tasks/{task_id\}
10443
+ */
10444
+ taskName?: string | null;
10425
10445
  }
10426
10446
  /**
10427
10447
  * Response message for SiteSearchEngineService.FetchDomainVerificationStatus method.
@@ -12418,7 +12438,7 @@ export declare namespace discoveryengine_v1beta {
12418
12438
  */
12419
12439
  orderBy?: string | null;
12420
12440
  /**
12421
- * The user's search query. See SearchRequest.query for definition. The value must be a UTF-8 encoded string with a length limit of 5,000 characters. Otherwise, an `INVALID_ARGUMENT` error is returned. At least one of search_query or PageInfo.page_category is required for `search` events. Other event types should not set this field. Otherwise, an `INVALID_ARGUMENT` error is returned.
12441
+ * Optional. The user's search query. See SearchRequest.query for definition. The value must be a UTF-8 encoded string with a length limit of 5,000 characters. Otherwise, an `INVALID_ARGUMENT` error is returned. At least one of search_query or PageInfo.page_category is required for `search` events. Other event types should not set this field. Otherwise, an `INVALID_ARGUMENT` error is returned.
12422
12442
  */
12423
12443
  searchQuery?: string | null;
12424
12444
  }
@@ -14478,7 +14498,7 @@ export declare namespace discoveryengine_v1beta {
14478
14498
  */
14479
14499
  export interface Schema$GoogleCloudDiscoveryengineV1betaUserEvent {
14480
14500
  /**
14481
- * Extra user event features to include in the recommendation model. These attributes must NOT contain data that needs to be parsed or processed further, e.g. JSON or other encodings. If you provide custom attributes for ingested user events, also include them in the user events that you associate with prediction requests. Custom attribute formatting must be consistent between imported events and events provided with prediction requests. This lets the Discovery Engine API use those custom attributes when training models and serving predictions, which helps improve recommendation quality. This field needs to pass all below criteria, otherwise an `INVALID_ARGUMENT` error is returned: * The key must be a UTF-8 encoded string with a length limit of 5,000 characters. * For text attributes, at most 400 values are allowed. Empty values are not allowed. Each value must be a UTF-8 encoded string with a length limit of 256 characters. * For number attributes, at most 400 values are allowed. For product recommendations, an example of extra user information is `traffic_channel`, which is how a user arrives at the site. Users can arrive at the site by coming to the site directly, coming through Google search, or in other ways.
14501
+ * Optional. Extra user event features to include in the recommendation model. These attributes must NOT contain data that needs to be parsed or processed further, e.g. JSON or other encodings. If you provide custom attributes for ingested user events, also include them in the user events that you associate with prediction requests. Custom attribute formatting must be consistent between imported events and events provided with prediction requests. This lets the Discovery Engine API use those custom attributes when training models and serving predictions, which helps improve recommendation quality. This field needs to pass all below criteria, otherwise an `INVALID_ARGUMENT` error is returned: * The key must be a UTF-8 encoded string with a length limit of 5,000 characters. * For text attributes, at most 400 values are allowed. Empty values are not allowed. Each value must be a UTF-8 encoded string with a length limit of 256 characters. * For number attributes, at most 400 values are allowed. For product recommendations, an example of extra user information is `traffic_channel`, which is how a user arrives at the site. Users can arrive at the site by coming to the site directly, coming through Google search, or in other ways.
14482
14502
  */
14483
14503
  attributes?: {
14484
14504
  [key: string]: Schema$GoogleCloudDiscoveryengineV1betaCustomAttribute;
@@ -15199,7 +15219,7 @@ export declare namespace discoveryengine_v1beta {
15199
15219
  */
15200
15220
  syncMode?: string | null;
15201
15221
  /**
15202
- * Optional. Immutable. User-facing, version-independent label for this connector. May be shared by multiple connectors under the same (project, location, collection, data_source); tag-based lookup returns the one with the greatest create_time. Optional at Create time. Agent Designer resolves connectors via (data_source, tag) when set, falling back to the legacy resource-name lookup when unset, so connectors created before the tag-write launch continue to work without a backfill.
15222
+ * Optional. Immutable. User-facing, version-independent label for this connector. May be shared by multiple connectors under the same (project, location, collection, data_source); tag-based lookup returns the one with the greatest create_time. Optional at Create time. If the caller omits `tag`, the server auto-derives one from the collection_id (falling back to data_source, else a time-based `t-` sentinel). The auto-derived tag is subject to the same immutability guarantee as a caller-supplied one, so callers who care about the exact tag value should provide it explicitly rather than relying on the server default. Agent Designer resolves connectors via (data_source, tag) when set, falling back to the legacy resource-name lookup when unset, so connectors created before the tag-write launch continue to work without a backfill.
15203
15223
  */
15204
15224
  tag?: string | null;
15205
15225
  /**