A significant breaking change has been introduced: many properties across various schemas are now explicitly readOnly. If your integration previously wrote to fields such as toolDisplayNames in GoogleCloudDiscoveryengineV1AssistAnswer, delayedGlobalFeatureToggleStateAllowed or effectiveFeatures in GoogleCloudDiscoveryengineV1Engine, experienceState in GoogleCloudDiscoveryengineV1Project, or any of the feature toggle related fields within GoogleCloudDiscoveryengineV1WidgetConfigUiSettings and its sub-schemas, your code will now fail. These fields are now server-managed or output-only, providing internal state information rather than configurable parameters.
On the new features front, developers gain more granular control and visibility. GoogleCloudDiscoveryengineV1ActionConfig now supports customerManagedScopes, allowing you to specify custom OAuth scopes for connectors. The GoogleCloudDiscoveryengineV1Engine schema includes a new globalFeatureToggleState property, enabling control over the global rollout timing of features (e.g., DELAYED, SCHEDULED, GENERAL, EARLY). For project provisioning, GoogleCloudDiscoveryengineV1ProvisionProjectRequest now accepts a provisionIntent to specify whether provisioning is for the new Gemini Enterprise experience (PROVISION_INTENT_SOBI) or the classic one (PROVISION_INTENT_LEGACY). Furthermore, the GoogleCloudDiscoveryengineV1DynamicTool schema gains a readonly boolean property to indicate if a tool performs write operations. Finally, new output-only fields like GoogleCloudDiscoveryengineV1Engine.effectiveFeatures and the detailed GoogleCloudDiscoveryengineV1WidgetConfigUiSettingsFeatureToggleInfo schemas provide enhanced visibility into the resolved state and launch stages of various features.
