You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ebac419
Browse filesBrowse the repository at this point in the historyBrowse files
fix: validate instantiated job models with the template's extension context (#362)
create_job instantiated the target models with a bare constructor, so the
FEATURE_BUNDLE_1 length validators on Job.name, Environment.name,
EmbeddedFileText.name and EmbeddedFileText.filename ran without a parsing
context and fell back to the base limits, rejecting values that decode had
already accepted under the extension.
instantiate_model now seeds a ModelParsingContext from the root template's
declared extensions and constructs each target model with
model_validate(..., context=...). Resolved values (the job name) are still
checked against the extension-aware limit, matching the schema text and the
Rust implementation; literal fields keep the result decode already reached.
Models whose class binds no parsing-context type are constructed without a
context, exactly as before.
The two comments in _model.py that described instantiation as running
without a context are updated to match; no validator logic changes.
Signed-off-by: Yongzhi Wei <276409147+wyongzhi@users.noreply.github.com>
Co-authored-by: AlexTranAmz <167144297+AlexTranAmz@users.noreply.github.com>
0 commit comments