-
Notifications
You must be signed in to change notification settings - Fork 146
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
[Support Powertools for AWS Lambda]: LocalStack #2862
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Thank you Waldemar for deciding to publicly have LocalStack support Powertools for AWS Lambda 🎉 I know @am29d is already in touch with your team, and we both look forward to explore collaboration opportunities. |
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.7.0 version! |
Organization Name
LocalStack
Your Name
Waldemar Hummer
Your current position
CTO
(Optional) Company logo
https://awsmp-logos.s3.amazonaws.com/d23d1bcc-cfe5-4301-893b-8f30025074e4/f5a016996213129265ed0eb248157749.png
(Optional) Use case
We are using Powertools internally at LocalStack for our own cloud platform running on AWS (for logging/tracing, among other features).
We also see an increasing number of our users who are using the LocalStack AWS emulator in conjunction with Powertools, i.e., running Lambda functions on the local machine and then debug the state locally. (e.g., here are a few items in our issue tracker).
We have recently also started building out a couple of sample apps to illustrate Powerapps running on LocalStack, e.g., here.
Thanks and kudos for building this awesome tool - keep up the great work! 🚀
Also using other Powertools for AWS Lambda languages?
The text was updated successfully, but these errors were encountered: