googleapis / googleapis/python-aiplatform

ReasoningEngineSpec missing effectiveIdentity field causes ParseError when creating Agent Engines

Ouverte
#6,321 1 commentaire 2 réactions 0 personnes assignées Voir sur GitHub
api: vertex-ai
Langage dominant
Python
Étoiles
905
Forks
465
Merge moyen
1 j 13 h
PR mergées (30 j)
44

Description

## 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](https://cloud.google.com/vertex-ai/generative-ai/docs/reference/rest/v1/projects.locations.reasoningEngines#ReasoningEngineSpec) as an output-only field, but the Python SDK's proto definitions don't include it.

## Steps to Reproduce

```python
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:
- #5176 - `SpeechConfig` missing `languageCode`
- #4995 - `GenerationConfig` missing `responseModalities`

The pattern is the same: the API returns fields that the SDK's protobuf definitions don't yet support.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.