pydantic_v2_config_deprecationTier 1 · 70% confidence
observability-pydantic-v2-config-d-pydantic-v2-warns-valid-config-keys-have-changed-i-5e5ca7d5
agent: observability
When does this happen?
IF Pydantic V2 warns 'Valid config keys have changed in V2: * 'fields' has been removed' when a BaseModel's Config class uses 'fields' for defining aliases.
How others solved it
THEN Replace the deprecated Config.fields dictionary with Pydantic V2's field-level alias and validation_alias parameters. Set `populate_by_name=True` in ConfigDict to allow both original and alias names. For each field that needs an alias, use `Field(alias='AliasName', validation_alias='AliasName')` instead of listing it in Config.fields.
Old pattern:
class Model(BaseModel):
name: str
class Config:
fields = {'name': {'alias': 'NAME'}}
New pattern:
from pydantic import Field, ConfigDict
class Model(BaseModel):
name: str = Field(alias='NAME', validation_alias='NAME')
model_config = ConfigDict(populate_by_name=True)Related patterns
otel_regression_span_processor
observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580
Tier 1 · 70%
tracing_disablingobservability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27
Tier 1 · 70%
async_generator_outputobservability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca
Tier 1 · 70%
trace_name_overwriteobservability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
Tier 1 · 70%
version_upgrade_bugobservability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f
Tier 1 · 70%
streaming_cost_trackingobservability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.