willyg302/gulp-awslambda

A Gulp plugin for publishing your package to AWS Lambda

gulp-awslambda's Issues

gulp-zip isn't installed automatically

I went to use the tool and I need to install gulp-zip you might just add that to the config file.

Support lambda aliases & versioning?

Would it be possible to extend this to add support for Lambda's Aliases and Versioning? I would love the ability to separate deployment (upload a new version of a function) from release (re-point the alias at the chosen version).

where to store creds

Was wondering if it will pick up my creds file if I store it in the root of my project. Doesn't seem to currently be working. I've simply added .aws/credentials to the root of my project along with my gulp file but its throwing errors saying it can't find credentials.

side note: Is it possible to store creds in a different matter and have it be picked up. Maybe providing a path to a static JSON file?

Possible to leverage S3?

Would it be possible to add an option to create/update the lambda function so that it is based on an object inside S3 that is uploaded separately? I would prefer to upload the zip files to S3, then define lambdas that point there based on the S3 options of the code object -

var params = {
  Code: { /* required */
    S3Bucket: 'STRING_VALUE',
    S3Key: 'STRING_VALUE',
    S3ObjectVersion: 'STRING_VALUE'
  },
  ...
}

Publish unexpected key in params

README states:

Otherwise, you may simply specify Publish as a parameter. If both are provided, the value in lambda_params will take precedence.

If I add Publish to my params:

....
Runtime: 'nodejs4.3',
Publish: true,
Timeout: 3
...

I get:

[20:28:36] Error in plugin 'gulp-awslambda'
Message:
Unexpected key 'Publish' found in params
Details:
domainEmitter: [object Object]
domain: [object Object]
domainThrown: false

Support New Version NodeJS Runtime

Would it be possible to update the aws-sdk version to pick up the new nodejs4.3 runtime? I can help with a pull request if needed. Thx.

removing devDependencies

Hello willyg302,

Do you have a gulpfile using using gulp-awslamda which only copies the production node modules to aws? I'm trying to remove the devDependencies from being copied but am stuck on integrating gulp-install. Anyways, any help is appreciated.

Add support for publishing versions

AWS Lambda recently launched support for versions: http://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html

There is a corresponding update to the Javscript SDK, where both the updateFunctionCode and createFunction, now take a Publish property in the params object which can be set to true or false:

• http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Lambda.html#createFunction-property
• http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Lambda.html#updateFunctionCode-property

Please add support for it in your plugin.