Skip to content

Releases: Testlio/lambda-tools

Update setup script

05 Mar 11:52
Compare
Choose a tag to compare
v3.4.1

bump version

Add support for node 8

28 Feb 14:10
Compare
Choose a tag to compare
v3.4.0

node 8 support

Yarn based CircleCI flow

30 Oct 09:30
d3aad5c
Compare
Choose a tag to compare
Merge pull request #72 from Testlio/feature/use-yarn

Feature - use yarn

Circle 2.0 upgrade

17 Aug 07:53
Compare
Choose a tag to compare
  • Upgrade to latest Circle version
  • Build workflows for better orchestration

Fixed "out of memory" error

29 May 08:51
41e4dda
Compare
Choose a tag to compare

Some deploys returned "out of memory". Fixed to babel-core v6.26.0.

Added support for Node v6.10

23 Feb 10:05
Compare
Choose a tag to compare
v3.3.0

Bump version number

Fix for functions with more than 50 versions

09 Mar 13:19
Compare
Choose a tag to compare

Fixed a bug with deploys failing when a Lambda version count went over 50.

Add CLI options for configuring timeouts

05 Feb 14:54
Compare
Choose a tag to compare

This update adds the --ignore-timeout and --timeout <seconds> command-line options to the lambda run and lambda execute commands, overriding configuration files.

This is useful for local testing of long-running and complex lambdas that take much less time to execute in a production environment.

Allow prefixing all AWS resources

29 Jan 13:13
Compare
Choose a tag to compare

This change allows prefixing all AWS resources that LT uses, including the S3 bucket used for storing all assets on deployment. This was a blocker as previously only the first user of LT was ever really able to use it 😓 - all good now.

Also updated README to include information on the setup script and it's options.

Implementing a migration path to 3.0

13 May 06:58
Compare
Choose a tag to compare

This release ensures that the API Gateway custom resource that is used by CF will be able to migrate to the version that will be released alongside 3.0.

The main goal was to make sure that the CF resource that is currently used is correct and does not too eagerly delete stages and APIs. The next version will include a new resource that will likely start replacing the existing resources, and as such the two need to be able to not interfere with one another.

PLEASE RUN lambda setup BEFORE USING THIS VERSION