mirror of
https://github.com/serverless/serverless.git
synced 2026-01-25 15:07:39 +00:00
d7eea2005e
* - Adding support for restricting the executing alexa skill by id (serverless/serverless#4700) - Adding support for multiple `alexaSkill` events on a single function (allows multiple Alexa Skills on a single lambda) * Adding a comment on the `serverless.cli` addition when testing. * Updating templates to have the right `alexaSkill` syntax * Cleaning up Travis-CI's occasional errors with sinon stubs going wild (hopefully) (https://travis-ci.org/serverless/serverless/jobs/335361582 / https://travis-ci.org/serverless/serverless/jobs/335706593 / https://travis-ci.org/serverless/serverless/jobs/335682396) * one last test case to make sure the alexaSkill file will be fully covered. * PR notes * naming - Add a default suffix for alexaSkillLogicalId if undefined * Revert changes to createStack.test.js (#c967c8d956b3d96afbaefa7fbe3e6eb498ecdd7c) * createStack.test - reject with an Error, not with a promise that resolves to an error.
Read this on the main serverless docs site
Serverless Infrastructure Providers
Under the hood, the serverless framework is deploying your code to a cloud provider like AWS, Microsoft Azure, Apache OpenWhisk or Google Cloud functions.
Connecting your provider
To deploy functions, specify your provider in your service's serverless.yml file under the provider key and make sure your provider credentials are setup on your machine or CI/CD system.
# serverless.yml
service: my-service-name
provider:
name: aws