Support functionName, functionVersion and invokedFunctionArn property on clientContext #94
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.
Allow deployment of packages from an S3 bucket instead of always requiring an upload from the file system. This is useful in two scenarios:
(1) Package build is performed by a different process, but deployment has to be gated by some approval workflow
(2) Multiple lambda functions use the same code base - this requires multiple uploads of the exact same package, making the deployment quite slow.
This allows us to specify an optional values for functionName, functionVersion and invokedFunctionArn properties on the client context. These properties are described here: http://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-context.html.