-
Notifications
You must be signed in to change notification settings - Fork 154
Feature request: include parser feature in lambda layer #3100
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
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Note that this was also discussed in the Discord community. |
Hi @scratchclaggy, thank you for opening the issue. I'll assign the issue to you and will continue the discussion in the PR. Thank you again! |
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. |
This is now released under v2.9.0 version! |
Use case
I want to use the new parser feature in my lambdas but need to ship it with my code as it is not available in the lambda layer currently.
Solution/User Experience
We simply need to include the feature when building / publishing the lambda layers.
Alternative solutions
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: