Developers must update their code as several properties are now readOnly. This affects delayedGlobalFeatureToggleStateAllowed and effectiveFeatures in GoogleCloudDiscoveryengineV1Engine, GoogleCloudDiscoveryengineV1alphaEngine, and GoogleCloudDiscoveryengineV1betaEngine. Similarly, experienceState in GoogleCloudDiscoveryengineV1Project, GoogleCloudDiscoveryengineV1alphaProject, and GoogleCloudDiscoveryengineV1betaProject is now read-only. Other fields made read-only include toolDisplayNames in GoogleCloudDiscoveryengineV1alphaAssistAnswer and various feature toggle related fields within GoogleCloudDiscoveryengineV1alphaWidgetConfigUiSettings schemas. Any attempts to write to these fields will now fail.
You can now precisely manage feature rollout with the new globalFeatureToggleState enum in GoogleCloudDiscoveryengineV1Engine (and its alpha/beta counterparts), allowing states like DELAYED, SCHEDULED, GENERAL, and EARLY. The effectiveFeatures field provides a comprehensive, server-resolved view of all feature toggle states. Connectors gain more flexibility with customerManagedScopes in GoogleCloudDiscoveryengineV1ActionConfig, enabling custom OAuth scopes. Additionally, GoogleCloudDiscoveryengineV1alphaAgent now supports defaultPinned for agents, and GoogleCloudDiscoveryengineV1DynamicTool includes a readonly flag.
