-
Notifications
You must be signed in to change notification settings - Fork 421
[Support Lambda Powertools]: Guild #6335
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. |
Hi @travishaby! Thank you so much for opening this issue to support Powertools! We really love seeing that we are creating positive impacts for our customers and they want to support us! Guild seems like a really interesting platform for talent and skill development! If you have any feedback you'd like to share with us about Powertools, we're all ears! If you'd like to connect to a meeting, we're also more than happy to hear your use case. |
|
This is now released under 3.9.0 version! |
Hey @leandrodamascena 👋 Thanks for all the work on Powertools. I'm spinning up a serverless developer efficiency effort inside our org to level up teams with things like Powertools, so I will definitely reach back out once that's underway. Thanks in advance! |
Organization Name
Guild
Your Name
Travis Haby
Your current position
Staff Software Engineer
(Optional) Company logo
https://guild.com/_next/image?url=https%3A%2F%2Fa-us.storyblok.com%2Ff%2F1022650%2F0x0%2Ff5806a6978%2Fguild.svg%2Fm%2F&w=384&q=75&dpl=dpl_B6H54oMWE1wiPVksLtSgT4BkW9aV
(Optional) Use case
We use Powertools wherever we can to avoid writing boilerplate code. We use Powertools for logging, event handling, batch processing and parameter retrieval, just to name a few.
Also using other Powertools for AWS Lambda languages?
The text was updated successfully, but these errors were encountered: