All Versions
324
Latest Version
Avg Release Cycle
11 days
Latest Release
13 days ago

Changelog History
Page 32

  • v1.8.0 Changes

    February 28, 2017

    Non-Breaking Changes

    • ๐Ÿ›  Fixed bug with deployment progress monitoring (#3297)
    • ๐Ÿ›  Fixed "too many open files" error (#3310)
    • ๐Ÿ›  Fixed bug with functions lists loaded from a separate file using Serverless Variables (#3186)

    ๐Ÿ’ฅ Breaking Changes

    โœ‚ Removed IamPolicyLambdaExecution Resource

    ๐Ÿšš We've removed the IamPolicyLambdaExecution resource template and replaced it with inline policy within the role as it's been causing issues with VPC and bloating the CF template. This is a breaking change only for users who are depending on that resource with Ref or similar CF intrinsic functions.

    ๐Ÿ”„ Changed displayed function name for sls info

    ๐Ÿ“œ The function name displayed when you run sls info is now the short function name as found in serverless.yml rather than the actual lambda name to keep it more provider agnostic. This could be breaking for any user who is depending or parsing the CLI output.

    Meta

  • v1.7.0 Changes

    February 14, 2017
    • โž• Added CloudWatch event source (#3102)
    • ๐Ÿ›  Fixed average functions duration calculation in "sls metrics" output (#3067)
    • Added SLS_IGNORE_WARNINGS flag and logging upcoming breaking changes (#3217)
    • โฌ‡๏ธ Reduced memory consumption during zipping process (#3220)
    • ๐Ÿ›  Fixed bug when using LogGroup resources with custom roles (#3213)

    Meta

  • v1.6.1 Changes

    January 31, 2017

    ๐Ÿš€ A minimal patch release that fixes an issue with rendering README.md on npm registry.

  • v1.6.0 Changes

    January 30, 2017

    Important Note: This release includes breaking changes. If your services stopped working after upgrading to v1.6.0, please read the following section.

    ๐Ÿ’ฅ Breaking Changes

    ๐Ÿ”Š CloudWatch logs are created explicitly

    ๐Ÿš€ Up until this release, CloudWatch log groups were created implicitly by AWS/Lambda by default and were not included in your service stack. However, some users were able to easily reach the CloudWatch log group limits (currently at 500 log groups), and it wasn't an easy task to clear them all. Because of that we decided to explicitly create the log groups using CloudFormation so that you can easily remove them with sls remove. This was also optionally possible with the cfLogs: true config option.

    If your service doesn't have the cfLogs: true set, and one of the function has been invoked at least once (hence the log groups were created implicitly by AWS), then it's very likely that you'll receive a "log group already exists" error after upgrading to v1.6.0. That's because CF is now trying to create the already created log groups from scratch to include it in the stack resources. To fix this breaking change, simply delete the old log group, or rename your service if you must keep the old logs.

    โœ‚ Removed function Arns from CloudFormation outputs

    ๐Ÿš€ Up until this release, the output section of the generated CloudFormation template included an output resource for each function Arn. This caused deploying big services to fail because users were hitting the 60 outputs per stack limit. This effectively means that you can't have a service that has more than 60 functions. To avoid this AWS limit, we decided to remove those function output resources completely, to keep the stack clean. This also means removing the function Arns from the sls info command, and at the end of the deployment command.

    ๐Ÿš€ This is a breaking change for your project if you're depending on those function output resources in anyway, or if you're depending on function arn outputs from the deploy or info commands. Otherwise, your project shouldn't be affected by this change. Fixing this issue depends on your needs, but just remember that you can always create your own CF outputs in serverless.yml.

    ๐Ÿšš Moved getStackName() method

    ๐Ÿšš This is a breaking change for plugin authors only. If your plugin used the provider.getStackName() method, it has been moved to naming.js, and should be referenced with provider.naming.getStackName() instead.

    โœ‚ Removed the defaults property from serverless.yml

    ๐Ÿšš We've finally dropped support for the defaults property which we introduced in v1. All child properties should now be moved to the provider object instead.

    Non-breaking changes

    • ๐Ÿš€ Reduce memory consumption on deploy by at least 50% (#3145)
    • โž• Added openwhisk template to sls create command (#3122)
    • ๐Ÿ‘ Allow Role 'Fn::GetAtt' for Lambda role (#3083)
    • โž• Added Access-Control-Allow-Credentials for CORS settings (#2736)
    • โž• add Support for SNS Subscription to existing topics (#2796)
    • Function version resources are now optional. (#3042)
    • ๐Ÿ‘ Invoke local now supports python runtime. (#2937)
    • ๐Ÿ›  Fixed "deployment bucket doesn't exist" error (#3107)
    • ๐Ÿ‘ Allowed function events value to be variables (#2434)

    Meta

  • v1.5.1 Changes

    January 19, 2017

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fix bug with multi line values is given in IoT events (#3095)
    • โž• Add support of numeric template creation path (#3064)
    • ๐Ÿ›  Fix deployment bucket bug when using eu-west-1 (#3107)

    Meta

  • v1.5.0 Changes

    January 05, 2017

    ๐Ÿ”‹ Features

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fix VTL string escaping (#2993)
    • โฑ Scheduled events are enabled by default (#2940)
    • โšก๏ธ Update status code regex to match newlines (#2991)
    • โž• Add check for preexistent service directory (#3014)
    • ๐Ÿš€ Deployment monitoring fixes (#2906)
    • ๐Ÿ›  Credential handling fixes (#2820)
    • โฌ‡๏ธ Reduced policy statement size significantly (#2952)

    Meta

  • v1.4.0 Changes

    December 15, 2016

    ๐Ÿ”‹ Features

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fixed exit code for failed function invocations (#2836)
    • Stricter validation for custom IAM statements (#2132)
    • ๐Ÿ›  Fixed bug in credentials setup (#2878)
    • โœ‚ Removed unnecessary warnings during Serverless installation (#2811)
    • โœ‚ Removed request and response config when using proxy integration (#2799)
    • ๐Ÿ”จ Internal refactoring

    Meta

  • v1.3.0 Changes

    December 02, 2016

    ๐Ÿ”‹ Features

    ๐Ÿ‘Œ Improvements

    • ๐Ÿ“š Documentation improvements with serverless.yml file reference (#2703)
    • Display info how to use SLS_DEBUG (#2690)
    • โฌ‡๏ธ Drop event.json file on service creation (#2786)
    • ๐Ÿ”จ Refactored test structure (#2464)
    • โœ… Automatic test detection (#1337)

    ๐Ÿ› Bug Fixes

    • โž• Add DependsOn for Lamda functions and IamPolicyLambdaExecution (#2743)
    • โž• Add JSON data parsing for invoke command (#2685)
    • ๐Ÿ”จ Internal refactoring

    Meta

  • v1.2.0 Changes

    November 22, 2016

    ๐Ÿ”‹ Features

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fix --noDeploy flag to generate deployment files offline without needing internet connection (#2648)
    • Bring back the include packaging feature with the help of globs (#2460)
    • ๐Ÿ”จ Internal refactoring

    Meta

  • v1.1.0 Changes

    November 02, 2016

    Future breaking changes

    ๐Ÿš€ We will include the LogGroup for your Lambda function in the CloudFormation template in the future. This will break deployments to existing applications because the log group was already created. You will get a warning about this if you deploy currently. We will force this behaviour in a future release, for now you can set it through the cfLogs: true parameter in your provider config. This change will also limit the logging rights to only this LogGroup, which should have no impact on your environment. You can read more in our docs.

    ๐Ÿ”‹ Features

    ๐Ÿ› Bugs

    • ๐Ÿ›  Fix variable syntax fallback if the file doesn't exist (#2565)
    • ๐Ÿ›  Fix overwriting undefined variables (#2541)
    • ๐Ÿ›  Fix CF deployment issue (#2576)
    • ๐Ÿ“ฆ Correctly package symlinks (#2266)

    Other

    Meta