Environment
- google-cloud-aiplatform version: 1.136.0
- google-adk version: 1.24.0
- Python version: 3.12
- OS: Ubuntu Linux (GCE VM)
Description
When creating a new Reasoning Engine using vertexai.agent_engines.create(), the API returns a response containing an effectiveIdentity field that is not defined in the local protobuf definitions, causing a ParseError.
The effectiveIdentity field is documented in the REST API reference as an output-only field, but the Python SDK's proto definitions don't include it.
Steps to Reproduce
import vertexai
from vertexai import agent_engines
vertexai.init(project="my-project", location="us-central1")
# This triggers the error when parsing the API response
engine = agent_engines.create(display_name="test_engine")
Error Message
Failed to parse spec field: Message type "google.cloud.aiplatform.v1.ReasoningEngineSpec" has no field named "effectiveIdentity" at "Operation.response.spec".
Available Fields(except extensions): "['sourceCodeSpec', 'serviceAccount', 'packageSpec', 'deploymentSpec', 'classMethods', 'agentFramework']".
Expected Behavior
The SDK should be able to parse the API response without errors. The effectiveIdentity field should be added to the ReasoningEngineSpec proto definition.
Additional Context
This is similar to:
The pattern is the same: the API returns fields that the SDK's protobuf definitions don't yet support.
Environment
Description
When creating a new Reasoning Engine using
vertexai.agent_engines.create(), the API returns a response containing aneffectiveIdentityfield that is not defined in the local protobuf definitions, causing aParseError.The
effectiveIdentityfield is documented in the REST API reference as an output-only field, but the Python SDK's proto definitions don't include it.Steps to Reproduce
Error Message
Expected Behavior
The SDK should be able to parse the API response without errors. The
effectiveIdentityfield should be added to theReasoningEngineSpecproto definition.Additional Context
This is similar to:
SpeechConfigmissinglanguageCodeGenerationConfigmissingresponseModalitiesThe pattern is the same: the API returns fields that the SDK's protobuf definitions don't yet support.