Azure Citadel
  • Blogs

  • ARM
  • Azure Arc
    • Overview
    • Azure Arc-enabled Servers
      • Prereqs
      • Scenario
      • Hack Overview
      • Azure Landing Zone
      • Arc Pilot resource group
      • Azure Monitoring Agent
      • Additional policy assignments
      • Access your on prem VMs
      • Create onboarding scripts
      • Onboarding using scripts
      • Inventory
      • Monitoring
      • SSH
      • Windows Admin Center
      • Governance
      • Custom Script Extension
      • Key Vault Extension
      • Managed Identity
    • Azure Arc-enabled Kubernetes
      • Prereqs
      • Background
      • Deploy Cluster
      • Connect to Arc
      • Enable GitOps
      • Deploy Application
      • Enable Azure AD
      • Enforce Policy
      • Enable Monitoring
      • Enable Azure Defender
      • Enable Data Services
      • Enable Application Delivery
    • Useful Links
  • Azure CLI
    • Install
    • Get started
    • JMESPATH queries
    • Integrate with Bash
  • Azure Landing Zones
    • Prereqs
    • Day 1
      • Azure Baristas
      • Day 1 Challenge
    • Day 2
      • Example
      • Day 2 Challenge
    • Day 3
      • Day 3 Challenge
    • Useful Links
  • Azure Policy
    • Azure Policy Basics
      • Policy Basics in the Azure Portal
      • Creating Policy via the CLI
      • Deploy If Not Exists
      • Management Groups and Initiatives
    • Creating Custom Policies
      • Customer scenario
      • Policy Aliases
      • Determine the logic
      • Create the custom policy
      • Define, assign and test
  • Azure Stack HCI
    • Overview
    • Useful Links
    • Updates from Microsoft Ignite 2022
  • Marketplace
    • Introduction
      • Terminology
      • Offer Types
    • Partner Center
    • Offer Type
    • Publish a VM Offer HOL
      • Getting Started
      • Create VM Image
      • Test VM Image
      • VM Offer with SIG
      • VM Offer with SAS
      • Publish Offer
    • Other VM Resources
    • Publish a Solution Template HOL
      • Getting Started
      • Create ARM Template
      • Validate ARM Template
      • Create UI Definition
      • Package Assets
      • Publish Offer
    • Publish a Managed App HOL
      • Getting Started
      • Create ARM Template
      • Validate ARM Template
      • Create UI Definition
      • Package Assets
      • Publish Offer
    • Managed Apps with AKS HOL
    • Other Managed App Resources
    • SaaS Offer HOLs
    • SaaS Offer Video Series
      • Video 1 - SaaS Offer Overview
      • Video 2 - Purchasing a SaaS Offer
      • Video 3 - Purchasing a Private SaaS Plan
      • Video 4 - Publishing a SaaS Offer
      • Video 5 - Publishing a Private SaaS Plan
      • Video 6 - SaaS Offer Technical Overview
      • Video 7 - Azure AD Application Registrations
      • Video 8 - Using the SaaS Offer REST Fulfillment API
      • Video 9 - The SaaS Client Library for .NET
      • Video 10 - Building a Simple SaaS Landing Page in .NET
      • Video 11 - Building a Simple SaaS Publisher Portal in .NET
      • Video 12 - SaaS Webhook Overview
      • Video 13 - Implementing a Simple SaaS Webhook in .NET
      • Video 14 - Securing a Simple SaaS Webhook in .NET
      • Video 15 - SaaS Metered Billing Overview
      • Video 16 - The SaaS Metered Billing API with REST
  • Microsoft Fabric
    • Theory
    • Prereqs
    • Fabric Capacity
    • Set up a Remote State
    • Create a repo from a GitHub template
    • Configure an app reg for development
    • Initial Terraform workflow
    • Expanding your config
    • Configure a workload identity
    • GitHub Actions for Microsoft Fabric
    • GitLab pipeline for Microsoft Fabric
  • Packer & Ansible
    • Packer
    • Ansible
    • Dynamic Inventories
    • Playbooks & Roles
    • Custom Roles
    • Shared Image Gallery
  • Partner
    • Lighthouse and Partner Admin Link
      • Microsoft Cloud Partner Program
      • Combining Lighthouse and PAL
      • Minimal Lighthouse definition
      • Using service principals
      • Privileged Identity Management
    • Useful Links
  • REST API
    • REST API theory
    • Using az rest
  • Setup
  • Terraform
    • Fundamentals
      • Initialise
      • Format
      • Validate
      • Plan
      • Apply
      • Adding resources
      • Locals and outputs
      • Managing state
      • Importing resources
      • Destroy
    • Working Environments for Terraform
      • Cloud Shell
      • macOS
      • Windows with PowerShell
      • Windows with Ubuntu in WSL2
    • Using AzAPI
      • Using the REST API
      • azapi_resource
      • Removing azapi_resource
      • azapi_update_resource
      • Data sources and outputs
      • Removing azapi_update_resource
  • Virtual Machines
    • Azure Bastion with native tools & AAD
    • Managed Identities

  • About
  • Archive
  1. Home
  2. Terraform
  3. Using AzAPI
  4. Removing azapi_resource

Table of Contents

  • Introduction
  • Starting configuration
  • Update the main.tf
  • Upgrade the provider
  • Import the resource
  • Remove the azapi_resource
  • Summary

Removing azapi_resource

How do you safely remove an azapi_resource block and switch to a native resource without creating issues with your Terraform state?

Introduction

Date Description
2021-04-29 Azure Web PubSub in Public Preview
2021-08-02 Developers start testing the preview functionality
2021-11-16 Azure Web PubSub goes GA
2021-12-06 Developers ask to include Web PubSub in the Terraform config
2022-01-28 azurerm v2.94: new resource azurerm_web_pubsub
2022-02-07 Switch to native support for the resource

With v2.94, the azurerm provider has caught up a little and has its first version of the resources and data sources for the Azure Web PubSub Service. https://registry.terraform.io/providers/hashicorp/azurerm/2.94.0/docs/resources/web_pubsub

Time to switch to the native resource and clean up our temporary azapi_resource.

Starting configuration

Your main.tf file should be similar to this:

terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "=2.93"
    }

    azapi = {
      source  = "azure/azapi"
      version = "=0.3.0"
    }
  }
}

provider "azurerm" {
  features {}
}

provider "azapi" {}

resource "azurerm_resource_group" "azapi_labs" {
  name     = "azapi_labs"
  location = "West Europe"
}

resource "azapi_resource" "webpubsub" {
  type      = "Microsoft.SignalRService/WebPubSub@2021-10-01"
  name      = "azapi-labs-richeney"
  parent_id = azurerm_resource_group.azapi_labs.id
  location  = azurerm_resource_group.azapi_labs.location

  body = jsonencode({
    sku = {
      name = "Free_F1"
      capacity = 1
    }
  })
}

⚠️ You should have a different value for your azapi_resource.webpubsub.name.

Update the main.tf

  1. Update the required azurerm version

    Update to v2.94:

    terraform {
      required_providers {
        azurerm = {
          source  = "hashicorp/azurerm"
          version = "=2.94"
        }
    
        azapi = {
          source  = "azure/azapi"
          version = "=0.3.0"
        }
      }
    }
    
  2. Add the azurerm_web_pubsub resource

    Add the block for the native resource.

    resource "azurerm_web_pubsub" "webpubsub" {
      name                = "azapi-labs-richeney"
      resource_group_name = azurerm_resource_group.azapi_labs.name
      location            = azurerm_resource_group.azapi_labs.location
      sku                 = "Free_F1"
      capacity            = 1
    }
    

    ⚠️ Remember to change the name to match your existing Azure Web PubSub resource.

Upgrade the provider

Terraform does not automatically update versions.

Running terraform validate with the current v2.93 provider will display an error message saying that The provider hashicorp/azurerm does not support resource type "azurerm_web_pubsub"..

Running terraform init with no arguments will display an error including locked provider registry.terraform.io/hashicorp/azurerm 2.93.0 does not match configured version constraint 2.94.0.

  1. Initialise

    Use the -upgrade switch.

    terraform init -upgrade
    

    Terraform will install azurerm v2.94.

Import the resource

Running terraform plan will show that it will create the azurerm_web_pubsub.webpubsub resource.

Running terraform apply will fail as the resource exists.

  1. Get the resource ID

    id=$(az webpubsub list --resource-group azapi_labs --query [].id --output tsv)
    
  2. Import the resource

    terraform import azurerm_web_pubsub.webpubsub $id
    

    The resource will be imported into state. Running terraform plan at this point will show that Terraform has a clean diff.

  3. List the identifiers

    terraform state list
    

    Expected output:

    azapi_resource.webpubsub
    azurerm_resource_group.azapi_labs
    azurerm_web_pubsub.webpubsub
    

Remove the azapi_resource

  1. Remove the azapi_resource block from main.tf

  2. Remove from the state file

    terraform state rm azapi_resource.webpubsub
    
  3. List the identifiers

    terraform state list
    

    Expected output:

    azurerm_resource_group.azapi_labs
    azurerm_web_pubsub.webpubsub
    

    Sure enough, the azapi_resource has been cleared up. We are fully azurerm native.

Running terraform plan will confirm that there are no planned changes.

Summary

You have successfully switched from an azapi_resource:

  1. upgraded the provider
  2. added the native resource
  3. imported the resource into state
  4. cleaned up the config
  5. removed the azapi_resource from state

In the next lab you will use azapi_update_resource.

azapi_resource Removing azapi_resource azapi_update_resource