grunt-aws-lambda icon indicating copy to clipboard operation
grunt-aws-lambda copied to clipboard

A grunt plugin to assist in developing functions for AWS Lambda.

Results 44 grunt-aws-lambda issues
Sort by recently updated
recently updated
newest added

To enable the AWS security token service and the possible to assume roles in different accounts I updated the aws-sdk dependency. Works for me, the only issue I had was...

Provides a function to invoke lambda with a event.json, but doesn't provide a facility to verify the response from the function. What is the purpose of this `lambda_invoke` without verification?

As the commit message mentions, this adds an expect_fail option. The expectation is that this could be used in an "integration test" suite, of sorts.

Hi, Aliases and Versions are not created when executing the 'deploy' command. The Grunt task has the following configuration: ``` lambda_deploy: { default: { 'arn':'MyFunction', options: { aliases: 'beta', enableVersioning:...

The `lambda_package` task ignores any errors from `npm.comands.install`, which results in incorrect zip files with no indication that they are not complete.

Would be nice if the function was created if not present...

I don't think there is a way yet to do this. I'm generating multiple entries in lambda_invoke to execute different event files. But that doesn't allow for coverage.

In lambda the environment variable LAMBDA_TASK_ROOT is exported to the root of the unpacked archive. But grunt-aws-lambda does not seem to export it.

I am working with versioning my lambda functions and I am realizing two things. 1. I cannot verify that the code I have locally has been deployed (either "deployed to...