Skip to main content

Azure Static Web App–Deploy using Bicep

As a follow-up on the presentation I did at CloudBrew about Azure Static Web Apps I want to write a series of blog posts.

So far I’ve deployed our Azure Static Web App using Github Actions. But if you prefer to use an Infrastructure as Code(IaC) approach, I have good news! Because in this post I’ll show you how to deploy your SWA using Bicep.

If you are completely new to Bicep, I suggest to first take a look at the documentation to get a good introduction.

In short Bicep is a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources. In a Bicep file, you define the infrastructure you want to deploy to Azure, and then use that file throughout the development lifecycle to repeatedly deploy your infrastructure.

It can be seen as an alternative for using ARM templates. The JSON syntax to create an ARM template can be verbose and require complicated expressions. Bicep syntax reduces that complexity and improves the development experience. During deployment, the Bicep CLI converts a Bicep file into ARM template JSON.

To help you get started I would recommend to install the Bicep extension in VS Code.

Ok, now that we have all the tooling in place, let’s focus on writing our Bicep file. Here is a simple example:

I will not go to through all the details but the most important settings are:

  • name: name of the resource
  • location: location of the resource
  • provider: the provider that submitted the last deployment to the primary environment of the SWA
  • repositoryUrl: URL for the repository of the SWA
  • branch: the target branch in the repository

Certainly check out the other settings to see all the things you can tweak and configure.

Remark: This requires that all access rights are configured correctly at the Github repository level.

We can directly deploy our Azure Static Web App through the Azure CLI:

az deployment group create --name YourDeploymentName --resource-group YourResourceGroupName --mode Incremental --template-file astro.bicep

Or you can integrate it into your deployment pipeline.

Here is an example using Azure Devops:

And one using Github Actions:

More information

Bicep language for deploying Azure resources - Azure Resource Manager | Microsoft Learn

Microsoft.Web/staticSites - Bicep, ARM template & Terraform AzAPI reference | Microsoft Learn

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.