A project created from the azure-nodejs template of the Serverless Framework.
This project requires that Serverless be installed as a global package.
npm install -g serverless
To create a new Azure function, run the following
serverless create --template azure-nodejs
To add more functions to the project, run the following
serverless func add -n YOUR_FUNCTION_NAME
Alternatively to delete a function from the project, run the following
serverless func remove -n YOUR_FUNCTION_NAME
Edit the serverless.yml definitions to match the Azure settings for region, function prefix, subscription id, and resource group.
Then issue a deployment
serverless deploy
| Function | Event | Description |
|---|---|---|
| RunSitesHeartbeat | Timer | Loops through a list of sites on a timer interval to prevent their Application Pools from idling. |
| NotifySiteUpdatedMailer | Http | Receives a subject, to email address, sites list (comma separated), and source text via POST; then sends a notification email. |
Consumption Azure functions' first million executions are free. Therefore functions can supplement other workflows at any scale.
Source: https://azure.microsoft.com/en-gb/pricing/details/functions/
Below are use case examples of how these functions are currently used.
| Function | Case |
|---|---|
| RunSitesHeartbeat | Implements the 'Always On' feature that is unavailable with B1 instances of Web Apps by calling the list of sites every 15 minutes. |
| NotifySiteUpdatedMailer | Sends an email notification after a GitHub workflow showing that the deployment was successful. |
Serverless Framework might have issues determining the correct authenticated account subscription with the following error
The access token is from the wrong issuer 'https://sts.windows.net/TENANT_ID/'. It must match the tenant 'https://sts.windows.net/DIFFERENT_TENANT_ID/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/DIFFERENT_TENANT_ID' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later.
The recommended method of authentication the deployment process is to use an Azure Service Principal that has permissions to write to resource groups in the given subscription. These instructions can be found at https://github.com/serverless/serverless-azure-functions#advanced-authentication
With a tenant that has multiple directory subscriptions, the serverless deploy method might have problems authenticating the current user. By default the configuration file found in the directory below, will contain the authentication token of the current user.
~/.Azure/slsTokenCache.json
Run the following Azure PowerShell cmdlets to retrieve the correct authentication token per subscriptions.
Connect-AzAccount
If the above command connects to the incorrect tenant then use the following which will generate a token locally.
Connect-AzAccount -TenantId YOUR_TENANT_ID -UseDeviceAuthentication
Switch the current context to the actual subscription on the tenant
Set-AzContext -Subscription "YOUR SUBSCRIPTION NAME"
Confirm that the access token has been created with the correct tenant id
Get-AzAccessToken
Copy the token to the clipboard to paste into the Serverless Framework Azure configuration file.
(Get-AzAccessToken).Token
Replace the authentication token in ~/.Azure/slsTokenCache.json with the token from the above command.
Use https://jwt.io/ to decrypt the tokens to confirm that the tid (tenant) id matches what Serverless expects to pass its authentication through.
All terms used are copyright to their original authors.