Two weeks have passed since our first v1 beta.1 release. Today we’re proud to announce the second beta version of the Serverless framework which introduces lots of new features, improvements and bug fixes.
You can install it via:
npm install -g serverless@beta
Here's what’s changed...
CORS support for API Gateway is finally here!
You can now enable CORS support with a simple cors: true in your http event definition:
functions: foo: handler: handler.handler events: - http: path: foo method: get cors: true
More in-depth documentation on how to e.g. set custom headers or the origin can be found in the corresponding CORS documentation.
A big thanks goes out to Chris Paton (@patoncrispy) who worked hard to get this into place for the beta.2 release!
Once you start to build more complex serverless applications you need the ability to set IAM roles for services your serverless functions access (e.g. access to a DynamoDB through a Lambda function).
This is now possible by defining an iamRoleStatement inside the provider property:
provider: iamRoleStatements: - Effect: Allow Resource: "*" Action: - dynamodb: *
This way Serverless will automatically add specified statements to service's IAM role.
You can read more about custom IAM role statements in the documentation.
We’ve updated the stack deployment and custom provider resource merging in this release so that your custom provider resources are merged once the initial stack is created.
This prevents the stack from being removed on initial stack creation when there’s an error with custom provider resource definitions.
Furthermore we’ll now support the merging / overwriting of everything with the help of the resources section in the
serverless.yml file. This makes the whole system way more powerful and extendable (if e.g. n event source is yet not supported via a plugin).
Take a look at this example taken from a
serverless.yml file which will add a DisplayName property to the
mySNSEvent and a Description to the
ServerlessDeploymentBucketName (this is the S3 bucket Serverless creates to store your deployment artifacts) output:
resources: Resources: mySNSEvent: Properties: DisplayName: 'Description for SNS topic' Outputs: ServerlessDeploymentBucketName: Description: 'Description for Serverless deployment bucket'
A big thank you goes out to @fridaystreet who was working on an initial prototype for this feature.
Ever wanted to look into the CloudFormation template Serverless will create? Or just wanted to get the deployment artifacts without an actual deployment?
This is now possible. Just run
serverless deploy --noDeploy to get the deployment artifacts inside the .serverless directory without an actual deployment (they’ll be removed when the next deployment is run).
Thank you John McKim (@johncmkim) for getting this up and running!
You can find the GitHub repository here: https://github.com/serverless/community-plugins
Plugins are the heart of the Serverless framework. We ship different core plugins right out of the box but there are many more use cases / functionality wishes where a plugin makes sense.
We’d like to introduce our new official community plugin repository in order to provide a way to explore great, high quality Serverless Plugins which are actively maintained by the contributors but also signed off by the Serverless team.
Feel free to contribute your Serverless plugin ideas / code there so that we can create a place where users can find great and useful Serverless plugins.
It's not a requirement everyone put plugins in here (absolutely keep them in your own repo if you want to,). However, we help maintain the ones in the community repository.
You can find the GitHub repository here: https://github.com/serverless/integration-test-suite
Serverless services and applications usually consist of different functions, events and maybe even more advanced custom resource definitions.
We’d like to ensure that the Serverless framework always meets the high quality standards you and your team has while developing modern, large scale serverless applications.
Our recently introduced integration test suite is used to test the Serverless framework autonomous in combination with complex services in real world scenarios.
We’ve just started the work on this one and would like to have your feedback / ideas regarding complex integration testing for the Serverless framework.
One of the feature requests we’ve heard over and over again is the setup of DynamoDB and Kinesis streams.
After some discussion with our awesome community we came to the conclusion that we don’t have enough feedback to build a complete plugin for those two event sources. That’s why we decided to add some documentation on how to setup those event sources with the help of custom provider resources.
Here’s an example how you can setup a Kinesis Stream:
# this code should be added to the `serverless.yml` file resources: Resources: mapping: Type: AWS::Lambda::EventSourceMapping Properties: BatchSize: 10 EventSourceArn: "arn:aws:kinesis:<region>:<aws-account-id>:stream/<stream-name>" FunctionName: Fn::GetAtt: - "<function-name>" - "Arn" StartingPosition: "TRIM_HORIZON"
You can find the whole documentation for those event sources here:
Furthermore we’d love to have your feedback on how you think the plugin solution for those event sources might look like. So feel free to join the conversation for the DynamoDB stream event here and Kinesis stream event source here.
Those are just the features we’ve decided to highlight in this announcement blog post.
You can find every issue and pull request in our corresponding Beta 2 Milestone.
Here are other features, improvements and fixes which will be also introduced in our beta 2 release.
Unfortunately we had a bug which caused problems when deploying endpoints via API Gateway as old stages were not successfully updated and function order in
serverless.yml caused trouble during deployment. While this has been resolved there is still an issue when functions get removed or renamed. API Methods are still deployed after a remove or rename and will only be fully removed on a following deployment. We're working with AWS to resolve this in the future.
This has been (partially) resolved thanks to the work from Jamie Sutherland (@wedgybo)
Pre-existing topic ARNs can now be used to hook to a function with the help of the SNS event.
Take a look at the documentation for the SNS event to see how this can be used.
We’ve switched the configuration syntax to camelCase so that it sticks to the overall defined coding convention.
After updating your SNS event definitions (e.g. from topic_name to topicName) everything should work again.
The deploy plugins lifecycle events are renamed so that the are more generalized and can be applied to more cloud providers.
We’ve not removed any lifecycle events but renamed them. You can see a list of the renaming here.
Furthermore you can see all new lifecycle event names here.
The variableSyntax can be overwritten with the help of the defaults property in the
serverless.yml file (You can see an example of a
serverless.yml file which overwrites this variableSyntax here).
Thank you John McKim (@johncmckim) for your work on this one!
The Serverless CLI had a very verbose output while loading / waiting for operations. This has been updated so that less screen real estate is used during usage. ### Include stage variables in API Gateway request body template
You can now access the stage variables with the help of the velocity request template. Take a look here to see how you can access it. Thank you Patrick Brandt (@patrickbrandt) for your work on this functionality. Fix for populating boolean and 0 variables See #1793 A bug caused problems with the population / usage of boolean and 0 variables. This has been resolved thanks to Kengo Suzuki (@kengos). ### Refactor for the API Gateway endpoints outputs See #1794 CloudFormation has a limit for 60 outputs per stack which means that you should be cautious what you want to put inside this outputs section. Nick den Engelsman (@nicka) pointed that out and worked on an improvement for the API Gateway outputs of the info plugin! ### Switch from node-zip to jszip
Zipping the service is one of our core functionalities. We’ve used the node-zip package for this task previously. However the package is a little bit dated so we’ve decided to move to the more maintained JSZip (which node-zip uses under the hood). This transition is finally implemented thanks to Chris Olszewski (@chris-olszewski). ### Alphabetical plugin sorting when running help command
Used plugins are displayed when you run the serverless --help command on your terminal. Sander van de Graaf (@svdgraaf) submitted a fix which sorts those plugins by name which makes it way easier to grasp what plugins are in use. ### Removed individual lodash function requires
Individual lodash function requires makes it tedious to work on code which uses the lodash library heavily. Sander van de Graaf (@svdgraaf) took some time to refactor the code so that the individual requires are removed. ## Breaking changes Moving fast and evaluation new ideas means that introducing some breaking changes are unavoidable. Here’s the list of all the the breaking changes you need to be aware of for this release: - camelCase syntax for SNS event configuration - New lifecycle event names for deploy plugin ## A big “thank you” to our awesome community
We couldn’t have introduced such a large feature set for this release without the invaluable feedback and help from our incredible community who is always active on GitHub, Gitter, our Serverless forum and everywhere else on the internet!
Thank you for making it a joy to work on Serverless everyday. # You want to contribute / give feedback? You want to contribute to the Serverless project? That’s awesome! We’ve recently introduced the following issue / pull request labels which makes it easy help us build a great Serverless framework:
Philipp Müns is a core developer at Serverless, Inc.