We’re in the process of scaffolding out our Microsoft Azure environments using Terraform. We’re looking at deploying consistently from master going forward, but our new infrastructure design requires explicit swapping of staging slots to production. We want this to happen automatically though in our development environment, ensuring we’re always using the latest code as we try things out in the cloud.

Many items in Terraform are supported in a first-class manner. However, sometimes you find an item not currently supported. In the case of Azure, we can specify absent Terraform provider functionality we need using ARM templates. It’s a bit more verbose to setup than a simple built-in property, but it works.

Here’s the code:

Terraform

Assuming azurerm_app_service.app_service and azurerm_app_service_slot.app_service_slot are available (update this template as needed):

resource "azurerm_template_deployment" "app_service_auto_swap" {
  name                = "my-app-service-auto-swap" 
  resource_group_name = "YOUR_RESOURCE_GROUP_NAME"
  deployment_mode     = "Incremental"

  template_body = "${file("./path/to/app-service-slot-auto-swap.json")}"

  parameters {
    "existingWebAppLocation" = "eastus"
    "webAppName"             = "${azurerm_app_service.app_service.name}"
    "slotName"               = "staging"
    "autoSwapSlotName"       = "production"
  }

  depends_on = [
    "azurerm_app_service.app_service",
    "azurerm_app_service_slot.app_service_slot"
  ]
}

ARM Template

app-service-slot-auto-swap.json

{
  "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "existingWebAppLocation": {
      "type": "string",
      "metadata": {
        "description": "App location"
      }
    },
    "webAppName": {
      "type": "string",
      "metadata": {
        "description": "Example: app-name"
      }
    },
    "slotName": {
      "type": "string",
      "metadata": {
        "description": "Example: staging"
      }
    },
    "autoSwapSlotName": {
      "type": "string",
      "metadata": {
        "description": "Example: production"
      }
    }
  },
  "resources": [
    {
      "type": "Microsoft.Web/sites/slots",
      "name": "[concat(parameters('webAppName'), '/', parameters('slotName'))]",
      "apiVersion": "2015-08-01",
      "location": "[parameters('existingWebAppLocation')]",
      "properties": {
        "siteConfig": {
          "autoSwapSlotName": "[parameters('autoSwapSlotName')]"
        }
      }
    }
  ]
}

Published Feb 25, 2019 by

Azure

Terraform

What Works and What Doesn't With ConfigurationMan...

Regex Performance With and Without RegexOptions.C...

z-index Is Confusing, but It Doesn't Have to Be

Logging ASP.NET Web API 2 Failed Request Body to ...

Using forEach for IE 11

Understanding Dart Sass modules and namespaced va...

Autofac: Eager vs Lazy Construction During Regist...

Writing a Browser Compatible Date Input

Non Pro/Premier SendGrid Accounts May Have Issues...

Vue 3 Composition API

Upcoming Google Chrome SameSite Change Breaks Our...

A Case Of Newtonsoft.Json, TypeNameHandling.All, ...

Ordering of static fields in C# matters

Avoiding a LINQ FirstOrDefault mishap

Artifact Conference 2019

How to Work with NPM Packages Locally Using .tgz ...

Caching Git LFS in AppVeyor to Avoid Large GitHub...

UX/UI Solutions: Make Content Less Overwhelming.

Takeaways from An Event Apart

ChatOps at RIMDev Using Probot

Setting Azure Web App Slot Auto Swap Using ARM Templates and Terraform

Terraform

ARM Template

Comments

Setting Azure Web App Slot Auto Swap Using ARM Templates and Terraform

Terraform

ARM Template

Working At Work: This And Other Thoughts On High Availability

Our DevOps Journey: Release Branches, Highly Available Azure Web Apps, and Terraform

IIS Rewrite Maps and Redirecting On Url Paths

Hugo Error Pages With IIS In Windows Azure

Running an AppVeyor Build After Creating an Azure Web App Using Terraform

Export CSV Table of All Azure Web Apps Configuration in Subscription

Comments