-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
provider/aws: Add support for updating Lambda function #5239
Merged
radeksimko
merged 5 commits into
hashicorp:master
from
MeredithCorpOSS:f-aws-lambda-func-updates
Mar 11, 2016
+356
−15
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
4aeb5bb
Adding support for Lambda function updates
robzienert b5c7521
aws_lambda_function: Force code update on SHA sum mismatch
fdc21aa
provider/aws: Simplify update logic for Lambda function
d777141
provider/aws: Add tests for Lambda function updates
9f6b487
provider/aws: Document lambda_function updates
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this was already here, but noting that this is an exception to our normal policy of "prefer file contents to paths" - I assume it's made complicated by Lambda function files being zips and potentially large.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that consistency (i.e. preference of
content = "${file()}
overpath
) would be nice, but I share the same concerns you mentioned. It will always be a ZIP file (= in terms of readability practically garbage unless we are base64-encoding/decoding it) and potentially big which may not be any good fortfstate
files.