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
Resolves #12 - Enables support for YAML anchors and metadata fields in
AgentsManifestconfiguration files.Changes
New Features
.,_, andx-for YAML anchors and custom metadata&default_settings) and reference them (e.g.,*default_settings) to reduce configuration duplicationImplementation
src/agentpool/models/manifest.py:extra="allow"inmodel_configto accept extra top-level fields@model_validator(mode="after")to validate and warn about unknown fieldstests/manifest/test_metadata_fields.py:.anchor,_meta,x-custom)Test Coverage
All tests passing (27/27):
Example Usage
Technical Details
validate_extra_fields()method checks all extra top-level keys.(dot) - for YAML anchors and hidden fields_(underscore) - for internal/metadata fieldsx-- for custom extensions (following OpenAPI convention)"Unknown field '{key}' in manifest. This field will be IGNORED."Related Issue
Fixes #12