icfnext / aws-lambda-toolkit Goto Github PK

zip is an invalid command on windows, so the toolkit can't be fully utilized.

Allow for distinct deployment configurations for various stages of development (dev, qa, prod, etc).

As requested by @pmichelotti, it would be pretty rad if the toolkit could be installed globally and then used to generate new lambda projects to further speed up the lambda creation process.

For example:

$ aws-lambda-toolkit new
Lambda name: authentication-service
Lambda region: us-east-1
Lambda description: It makes people authenticate and stuff

From there it would generate a folder in the CWD called authentication-service with a scaffolded example structure with the proper variables pre-filled in for the configuration files:

authentication-service/
    .awstoolkitconfig.json
    package.json
    index.js

Deployment shouldn't assume the user wants to increment the lambda version; not everybody wants 48,000 versions for all of their lambdas.

Could probably add an argument to the deployment method for incrementing so it doesn't force everybody to have more lambda versions than necessary.