How to Import an Azure Container Registry Webhook into Terraform

Import Azure Container Registry Webhook with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Container Registry resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Container Registry Webhook to managed Terraform.

terraback scan all azure --subscription-id YOUR_ID

terraback azure import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

import {
  to = azurerm_container_registry_webhook.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.ContainerRegistry/registries/prodacr/webhooks/deployhook"
}

Example azurerm_container_registry_webhook configuration

Here is a realistic Azure Container Registry Webhook block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "azurerm_container_registry_webhook" "main" {
  name                = "deployhook"
  resource_group_name = "prod-rg"
  registry_name       = "prodacr"
  location            = "eastus"
  service_uri         = "https://example.com/webhook"
  actions             = ["push"]
  status              = "enabled"
}

Gotchas when importing a Azure Container Registry Webhook

• The webhook is a child of the registry: its ARM ID nests under .../registries/<registry>/webhooks/<name>, and registry_name must reference the parent registry.
• location must match the registry's region (or a replica region); a mismatch is rejected at apply.
• actions is a required set such as ["push", "delete"]; an empty list is invalid.
• custom_headers can contain authentication tokens and is sensitive; review the generated block before committing it.

Doing it manually with terraform import

The native approach is to write the azurerm_container_registry_webhook block by hand, then run terraform import azurerm_container_registry_webhook.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import other Azure resources