Maintenance: Remove email-validator dependency for v2

[rubenfonseca]

Summary

We should remove the email-validator dependency from the v2 Lambda Layer and SAR.

Why is this needed?

As we try to reduce the size of our v2 layer, we noticed that the email-validator is only needed if you use the pydantic's EmailStr validator.

Currently, adding email-validator adds ~400KB to our compressed layer size.

Which area does this relate to?

Validation

Solution

No response

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

[ran-isenberg]

@rubenfonseca i think this removal will break the parser SES model that expect this depedancy during import.

from pydantic.networks import EmailStr

is 400KB really that big of a deal?

[rubenfonseca]

Hi @ran-isenberg! Thanks for your feedback! We thought about the cost-benefit of adding an extra dependency to validate something that is sent by AWS, and that the user (AFAIK) has little to no control. We believe it's not worth it and we could use a simple string validation instead.

400KB might not seem a very big deal, but currently is twice the size of Powertools :) We could do a lot more with that space!

I also just update the PR to remove the dependency you mentioned during the import, so hopefully no crashes during import :)

[heitorlessa]

linking the original issue by @huonw #998

and linking Pydantic ~330ms overhead at cold start (largely due to reflection; it's expected to get a lot better in Pydantic V2): #1164 (comment)

[heitorlessa]

Closing as we're wrap to launch V2

[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.