Add serverless-lambda-layer-packager#291
Merged
Merged
Conversation
eahefnawy
approved these changes
Sep 24, 2019
Contributor
eahefnawy
left a comment
eahefnawy
left a comment
There was a problem hiding this comment.
Thanks for sharing @bramhoven 😊
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This Serverless plugin allows you to maintain your normal project structure when developing your Lambda Layer, and you do not have to think about it getting packaged in the correct folder.
Let's say you are making a Python Lambda function with a Python layer, that layer's code will have to be put inside a python/{packagename} folder inside your layer's zip file. This python folder clutters up your workspace and with this plugin, you do not have to think about it. It will put your code inside the correct folder when Serverless packages your layer.