The Serverless Application template creates an infrastructure as code project in your favorite language that deploys a serverless application to Azure with Pulumi. It deploys an Azure Blob Storage account configured for static website hosting and an Azure Function written in the same language as the template. The template ships with placeholder content to give you a working project out of the box that you can customize easily and extend to suit your needs.
Using this template
To use this template to deploy your own serverless application, make sure you’ve installed Pulumi and configured your Azure credentials, then create a new project using the template in your language of choice:
$ mkdir my-serverless-app && cd my-serverless-app $ pulumi new serverless-azure-typescript
$ mkdir my-serverless-app && cd my-serverless-app $ pulumi new serverless-azure-python
$ mkdir my-serverless-app && cd my-serverless-app $ pulumi new serverless-azure-go
$ mkdir my-serverless-app && cd my-serverless-app $ pulumi new serverless-azure-csharp
$ mkdir my-serverless-app && cd my-serverless-app $ pulumi new serverless-azure-yaml
Follow the prompts to complete the new-project wizard. When it’s done, you’ll have a complete Pulumi project that’s ready to deploy and configured with the most common settings. Feel free to inspect the code in
Deploying the project
The template requires no additional configuration. Once the new project is created, you can deploy it immediately with
$ pulumi up
When the deployment completes, Pulumi exports the following stack output values:
- The HTTP URL of the static website.
- The HTTP URL of the serverless function endpoint.
Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed
siteURL, for example, can be used from the command line to open the newly deployed website in your favorite web browser:
$ open $(pulumi stack output siteURL)
Customizing the project
Projects created with the Serverless Application template expose the following configuration settings:
- The path to the folder containing the files of the website. Defaults to
www, which is the name (and relative path) of the folder included with the template.
- The path to the folder containing the serverless functions to be deployed. Defaults to
app, which is also included with the template.
- The file to use for top-level pages. Defaults to
- The file to use for error pages. Defaults to
All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default,
Pulumi.dev.yaml) or by changing their values with
pulumi config set.
$ pulumi config set sitePath ../my-existing-website/build $ pulumi up
You can cleanly destroy the stack and all of its infrastructure with
$ pulumi destroy
Congratulations! You’re now well on your way to managing a production-grade serverless application on Azure with Pulumi — and there’s lots more you can do from here: