Several properties have been made read-only/immutable, which is a breaking change. Specifically, delayedGlobalFeatureToggleStateAllowed and effectiveFeatures in GoogleCloudDiscoveryengineV1Engine (and its alpha/beta counterparts), experienceState in GoogleCloudDiscoveryengineV1Project (and alpha/beta), and toolDisplayNames in GoogleCloudDiscoveryengineV1alphaAssistAnswer (and beta) can no longer be modified. If your applications attempt to write to these fields, they will now encounter errors.
On the new features front, GoogleCloudDiscoveryengineV1ActionConfig (and v1alpha) now supports customerManagedScopes, allowing you to specify custom OAuth scopes for connectors that opt into this feature, providing more granular control over permissions. Engines gain new feature management capabilities with the globalFeatureToggleState property, enabling control over feature rollout strategies (e.g., DELAYED, SCHEDULED, GENERAL, EARLY), and the effectiveFeatures output-only map to see the resolved state of all feature toggles. When provisioning a project, GoogleCloudDiscoveryengineV1betaProvisionProjectRequest now includes a provisionIntent field, letting you specify the desired experience (SOBI_ONLY, LEGACY_ONLY). Finally, GoogleCloudDiscoveryengineV1DynamicTool (and v1alpha) introduces a readonly boolean property to indicate if a tool performs write operations, and GoogleCloudDiscoveryengineV1alphaAssistAnswer (and v1beta) now exposes toolDisplayNames for human-readable tool titles.
