Add top-level Model ID field to PydanticAI connection#62818
Merged
kaxil merged 1 commit intoapache:mainfrom Mar 3, 2026
Merged
Add top-level Model ID field to PydanticAI connection#62818kaxil merged 1 commit intoapache:mainfrom
kaxil merged 1 commit intoapache:mainfrom
Conversation
3ba4c51 to
2040442
Compare
Replace the repurposed `schema` field with a proper `conn-fields` entry in provider.yaml. This renders a dedicated "Model" input in the connection form that stores to `extra_dejson["model"]` — the same pattern used by 23+ providers (Google, Slack, Snowflake, etc.).
2040442 to
0d46b6f
Compare
gopidesupavan
approved these changes
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The LLM model identifier (e.g.,
anthropic:claude-sonnet-4-20250514) was previously only configurable via the JSONextrafield on the connection, requiring users to edit raw JSON. This repurposes the connectionschemafield as "Model ID" so users can set it directly in the connection form UI.Design
The
schemafield is a natural fit — it's a string field on every Airflow connection, was previously hidden for this connection type, and no AI provider needs it for its original purpose.Priority order for model resolution:
model_idparameter on the hook (highest)schemafield on the connection (shown as "Model ID" in the UI)extra["model"]on the connection (legacy, backward compatible)Changes
schema, relabel as "Model ID", add placeholderget_conn()readsconn.schemabetweenmodel_idparam andextra["model"]