-
Notifications
You must be signed in to change notification settings - Fork 1
feat: Generalize the construct to be usable by other PowerTools supported languages #52
Conversation
fed7ee1
to
bd74e52
Compare
This pull request is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. |
Closing this pull request as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
Closing this pull request as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
Closing this pull request as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
What's the plan here :) ? |
Sorry for the delay Florian. I am on it and will rename the project to make it more general for both runtimes. |
This pull request is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. |
Closing this pull request as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
Conflict resolved manually and merged PR 998b162 |
Lambda PowerTools for TypeScript is in a need to be able to build and deploy Lambda Layers for it's version of the library: aws-powertools/powertools-lambda-typescript#826
This PR generalize the construct to allow it to be reused by other runtimes and include the TypeScript version of it.
Next step would be to rename the construct package to be generic and not tailored to Python.
Tests
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.