Lambda-tools

This is a pre-release version. The functionality described below may change
before the final version is released.

Changes and bug fixes:

* Added more details to the help text for the commands.
* Rewrote command parsing code to make reuse easier.
* Removed a spurious print statement.

This is a pre-release version. The functionality described below may change
before the final version is released.

Test runner

Added a new command, `ltools test` and a corresponding `test` configuration
section. The test settings are as follows:

yaml
functions:
my_function:
test:
source: path to source folder containing tests
requirements:
requirements.txt file(s) to include with tests.
syntax is the same as for requirements section in build.
runner:
The test runner to use to run the tests.
Currently only unittest is supported.
ignore:
Files to ignore when copying tests into the bundle.
syntax is the same as for ignore section in build.


`bundle` setting

Before creating the zip package, the files are copied into a "bundle"
directory. In previous releases of lambda-tools, this was created in a
temporary, randomly-named directory generated by the system, and the user had no
control over where it was saved. As of version 0.2.0, you can now specify where
the bundle will be created:

yaml
functions:
my_function:
build:
bundle: build/bundle


`ltools clean` command

This will remove the bundle folder after running your tests.

Note: if you have not declared a `tests` section, the bundle folder will be
removed automatically after `ltools build` has completed. This preserves the
behaviour of version 0.1.

Version 0.0 configuration is no longer supported.

The initial configuration format from version 0.0 is no longer supported.
Additionally, the version number tag at the start of the configuration file
is now optional.

Changes in this release:

* Fixed an error when new lambda functions had tags specified.
* Switched to using `yaml.safe_load()` for secure loading of untrusted lambda definition files.
* Accept configuation files called `aws-lambda.json` instead of `aws-lambda.yml`.
* Note that since YAML is actually a superset of JSON, the YAML parser is still used here.

Adds support for the `ignore` directive, allowing you to ignore files while bundling.

Changes in this release:

* Added a `--terraform` option to `ltools build` to allow `ltools` to be used with Terraform's
[external data source](https://www.terraform.io/docs/providers/external/data_source.html).

Version 0.1.0 is the first alpha release. A lot of the code has been rewritten from the prealpha, and the configuration schema has changed significantly.

Lambda configurations are now divided into two sections: `build` and `deploy` which correspond to the `ltools build` and `ltools deploy` sections respectively. The `build` section is required; the `deploy` section is only needed if you want to use `ltools` to deploy your lambda function directly to AWS; if you are using another mechanism such as Terraform, you can omit it.

Full instructions on how to use this package are given in the readme file.