Add generateDefaultAlias flag #124
Open
Conversation
This file contains 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
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.
AWS Lambda hase a sum code size limit of 75GB.
Every new version of a lambda function goes towards this limit.
There are multiple cleanup scripts on the internet that can be used to clean old versions of lambda functions, none of which can delete a version when there are aliases set for it.
Aliases should generally only be used when we want to preserve a specific version for whatever reason.
This flag makes it possible to NOT generate an alias while uploading, unless one is explicitly set with the tag.
The default functionality is unchanged, so it's backwards compatible, it only has effect when configured.