Support JSON Schema referencing in validation utils (by using fastjsonschema's handlers param)

[danieljnchen]

Use case

fastjsonschema, which is used internally by aws-lambda-powertools' validation utilities, supports JSON Schema's schema referencing, but it by default launches an http request to the url provided. However, in the case that users don't want to launch an http request to fetch the referenced schemas (for example, because the references are stored locally), fastjsonschema also provides the handlers parameter to its validation methods (docs)

You can pass mapping from URI to function that should be used to retrieve remote schemes used in your definition in parameter handlers.

Solution/User Experience

Update aws-lambda-powertools' validation functions to support passing the handlers param to fastjsonschema's validate call. As far as I can tell, this would require adding the param to validate_data_against_schema and to the user-facing methods/decorators validate and validator

Alternative solutions

No response

Acknowledgment

• This feature request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[boring-cyborg]

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

[heitorlessa]

hey @danieljnchen, thanks for taking the time to cut a feature request and the investigation -- it makes total sense we support it.

Would you be interested in creating a PR? we can guide it. We're currently focused on fixing a release pipeline issue and V3, which means we have no ETA when this would be looked at right now.

Edit: it'd be great to have an escape hatch where customers could provide additional keyword arguments so they're not blocked in the futur

[danieljnchen]

@heitorlessa Thanks for the quick response! I'd be happy to make a PR -- I'll look through the contributing docs and hopefully have something up shortly

[danieljnchen]

@heitorlessa I've posted a draft PR: #4508

I had some difficulty getting the dev environment setup -- I used gitpod as directed in the Contributing guidelines, but make dev-gitpod failed, and I encountered a lot of missing dependencies when trying to run unit tests. What should I do to move this PR along?

[leandrodamascena]

@heitorlessa I've posted a draft PR: #4508

I had some difficulty getting the dev environment setup -- I used gitpod as directed in the Contributing guidelines, but make dev-gitpod failed, and I encountered a lot of missing dependencies when trying to run unit tests. What should I do to move this PR along?

Hi @danieljnchen, I'm seeing this comment now. Did you manage to resolve the problem with the environment?

[danieljnchen]

@heitorlessa I've posted a draft PR: #4508
I had some difficulty getting the dev environment setup -- I used gitpod as directed in the Contributing guidelines, but make dev-gitpod failed, and I encountered a lot of missing dependencies when trying to run unit tests. What should I do to move this PR along?

Hi @danieljnchen, I'm seeing this comment now. Did you manage to resolve the problem with the environment?

Thanks for checking in! Unfortunately not; here's the error I'm getting when I run make-devgitpod:

[leandrodamascena]

Hello @danieljnchen! Yes, I was able to reproduce this error and opened an issue to fix this. I'm working on it now and hope to finish it early next week.

#4530

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.