Developers can now define featurePolicies directly on GoogleCloudDiscoveryengineV1Engine resources (and their alpha/beta counterparts). This new capability allows you to specify allowedMembers and deniedMembers for individual features, along with a defaultAccess setting. Members are defined using the new GoogleCloudDiscoveryengineV1EngineFeaturePolicyMember schema, which includes id, type (USER/GROUP), and an optional displayName.
Breaking Change: The verification property within the GoogleCloudDiscoveryengineV1EngineFeaturePolicyMember schema (and its alpha/beta versions) has been made read-only. If your code previously attempted to write to this field, it will now fail. This field is now output-only, reflecting the server's directory check result.
Additionally, COMPLIANCE_LEVEL_ITAR has been added as a new enum value to GoogleCloudDiscoveryengineV1WidgetConfigCustomerProvidedConfig.complianceLevel, indicating support for ITAR compliance.
