- http://docs.aws.amazon.com/lambda/latest/dg/API_VpcConfig.html
- http://docs.aws.amazon.com/lambda/latest/dg/vpc.html
This allows users to place their Lambda functions in specific subnets with specific security groups.

- Check if the function exists, if it does update else create new
- This API provides compatibility with VpcConfig

VpcConfig support

Add -e to not escape \n when echo'ing

Merge upstream/master with kecaps:master

Add package command

Only ignore deploy.env by default

Updated readme: MODE is no longer a thing

Throw on failures

- Add editorconfig
- Ignore editorconfig

Private module fix

* Update to pass callback for nodejs4.3 runtime
* Default to recommended runtime
* Add note about runtimes
* Added note on how to target v0.10.36

* Post install script

…. (2) (motdotla#80)

This lets me e.g. exclude not only `.env` but by `.env.prod` / `.env.dev`
and any other junky / sample files that happen to live in the method's
directory.  Or for that matter to move all those files into a sub-
directory and exclude that.  Less policy, more flexibility.

* Ignore .swp files by default. Remove redundant deploy.env ignore from the examples.

… run command when running with a custom event file (motdotla#51)

* Add context.json example
* Add contextFile -x --contextFile parameter
* fix contextFile example filename
* update setup log message
* Runhandler: Hotfixes
* Reformat to match existing whitespace
*  more reformating to match existing whitespace
* revert version back to 0.7.1
* Fix indenting