-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maintenance: Ensure Bedrock Agents resolver works with Pydantic v2 #4196
Milestone
Comments
rubenfonseca
added
triage
Pending triage from maintainers
internal
Maintenance changes
labels
Apr 24, 2024
github-project-automation
bot
moved this to Triage
in Powertools for AWS Lambda (Python)
Apr 24, 2024
rubenfonseca
added
v3
Features that will be included in Powertools v3.
and removed
triage
Pending triage from maintainers
labels
Apr 24, 2024
2 tasks
7 tasks
This was referenced Jun 24, 2024
7 tasks
github-actions
bot
added
the
pending-release
Fix or implementation already in dev waiting to be released
label
Sep 11, 2024
7 tasks
Closing as completed. |
github-project-automation
bot
moved this from Backlog
to Coming soon
in Powertools for AWS Lambda (Python)
Sep 11, 2024
|
This is now released under 3.0.0 version! |
github-actions
bot
removed
the
pending-release
Fix or implementation already in dev waiting to be released
label
Sep 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why is this needed?
As we prepare to drop Pydantic v2, we need to ensure that the Bedrock Agents functionality still works. Bedrock Agents only accepts OpenAPI version 3.0, whereas Pydantic v2 generates schemas that are valid for OpenAPI 3.1.
Which area does this relate to?
Event Handler - REST API
Solution
Research shows that we can take an OpenAPI 3.1 schema and make it compatible with Bedrock Agents by doing some simple changes, like removing new fields and changing the schema version.
After implementing those we need to do extensive testing to ensure the feature is not broken when using Agents.
Acknowledgment
The text was updated successfully, but these errors were encountered: