Azure Functions Serverless Plugin
This plugin enables Azure Functions support within the Serverless Framework.
- Node.js v6.5.0+ (this is the runtime version supported by Azure Functions)
- Serverless CLI
v1.9.0+. You can run
npm i -g serverlessif you don't already have it.
- An Azure account. If you don't already have one, you can sign up for a free trial that includes $200 of free credit.
Create a new Azure service
- Create a new service using the standard Node.js template, specifying a unique name for your app:
serverless create -t azure-nodejs -p <appName>
- CD into the generated app directory:
- Install the app's NPM dependencies, which includes this plugin:
Deploy, test, and diagnose your Azure service
Deploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the
serverlessCLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.serverless deploy
Note: Once you've authenticated, a new Azure "service principal" will be created, and used for subsequent deployments. This prevents you from needing to manually login again. See below if you'd prefer to use a custom service principal instead.
Invoke a function, in order to test that it works:serverless invoke -f hello
Stream the output logs for your function:serverless logs -f hello
Make some code changes,
deployagain, view logs, etc. and provide us feedback on how to make the experience even better!
Note: If you're working on a single function, you can use the
serverless deploy function -f <function>command instead of
serverless deploy, which will simply deploy the specified function instead of the entire service.
If at any point, you no longer need your service, you can run the following command to remove the Azure Functions that were created, and ensure you don't incur any unexpected charges:
The getting started walkthrough illustrates the interactive login experience, which is recommended for most users. However, if you'd prefer to create an Azure "service principal" yourself, you can indicate that this plugin should use its credentials instead, by setting the following environment variables:
export azureSubId='<subscriptionId>'export azureServicePrincipalTenantId='<tenantId>'export azureServicePrincipalClientId='<servicePrincipalName>'export azureServicePrincipalPassword='<password>'
Please create issues in this repo for any problems or questions you find. Before sending a PR for any major changes, please create an issue to discuss.
We're still in the process of getting everying running 100%, but please refer to the Serverless contributing guidlines for information on how to contribute and code of conduct.