Lambda S3 object version defaults to '$LATEST' if unspecified #5370
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 is a rebased and polished version of #4770
Essentially I just resolved conflicts with some latest changes in the Lambda Function acceptance tests and replaced
rand.New(rand.NewSource(time.Now().UnixNano())).Int()
withacctest.RandInt()
.The original credit obviously goes to @Bowbaq 😉
I will merge this myself once Travis turns green since it's just polished version of someone else's PR and the changes were quite trivial, but feel free to do code review afterwards.
I also ran acceptance tests: