We're proud to release the Serverless Framework v1.3.0 today.
Let's take a look at the highlights of this release. You can find a list with all the updates in the changelog.
Ever wondered how your functions are performing? The new
serverless metrics allows you to see all the function metrics, such as invocations, throttles, errors, and duration, at a glance.
serverless metrics --function myFunction
to see the metrics of the last 24h for your function
You can even specify the timeframe you want to see for the metrics with the
serverless metrics --function myFunction --startTime 2016-11-28 --endTime 2016-12-02
will show you all the metrics between Nov. 28th and Dec. 2nd.
You can read more about the new metrics functionality in the documentation.
Setting up credentials should be streamlined in the overall Serverless experience. V1.3 adds a new command called
serverless config credentials that helps you setup your AWS credentials on your local machine.
This example will setup the
default AWS profile with the provided key and secret:
serverless config credentials --provider aws --key someKey --secret someSecret
No need to configure the
credentials file through the
You can read more about the new config functionality in the documentation.
Serverless now supports automatic Lambda versioning with the help of the built-in Lambda versions AWS provides.
Keeping a history of all of your deployed Lambda functions is an important feature. AWS will now use your Lambda version in the logs, as well. This makes it way easier to track down bugs.
You don't need to change anything. Just deploy your service as usual and Serverless will version your Lambda functions from now on.
We've also fixed a bunch of bugs (thanks for bringing them up!), and have continued our process of codebase refactorings so that it's easier for new contributors to get on board.
Note that we're using strict Semver for our Serverless Framework versioning. This way you'll know when we introduce major features or breaking changes.
Philipp Müns is a core developer at Serverless, Inc.