API template library

Azure Container Registry Tasks mock API and live sandbox

A WireMock simulation of Microsoft Azure's REST API — covering build task definitions, scheduled runs, and run logs.

Vendor
Microsoft Azure
Functionality
Build tasks and runs
Spec version
2019-04-01
Endpoints
13
Stubs
15
Protocol
REST
Validation
AI-validated Before publication, an AI agent exercised these endpoints against the real Microsoft Azure API through WireMock's recording proxy, and the recorded traffic was used to verify each stub's request and response shapes.

Live sandbox · no signup, no API key

Azure Container Registry - Resource Manager Registry Tasks

A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.

Base URL
https://dgegv.wiremockapi.cloud

POST Get build source upload URL

curl -s -X POST 'https://dgegv.wiremockapi.cloud/subscriptions/your-subscriptionId/resourceGroups/your-resourceGroupName/providers/Microsoft.ContainerRegistry/registries/your-registryName/listBuildSourceUploadUrl' \
  -H 'Content-Type: application/json' \
  -d '{}'

PUT Create task

curl -s -X PUT 'https://dgegv.wiremockapi.cloud/subscriptions/your-subscriptionId/resourceGroups/your-resourceGroupName/providers/Microsoft.ContainerRegistry/registries/your-registryName/tasks/your-taskName' \
  -H 'Content-Type: application/json' \
  -d '{}'

GET Get task

curl -s -X GET 'https://dgegv.wiremockapi.cloud/subscriptions/your-subscriptionId/resourceGroups/your-resourceGroupName/providers/Microsoft.ContainerRegistry/registries/your-registryName/tasks/your-taskName'
Method Path Summary
POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/listBuildSourceUploadUrl Registries_GetBuildSourceUploadUrl
GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs Runs_List
GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId} Runs_Get
PATCH /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId} Runs_Update
POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}/cancel Runs_Cancel
POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/runs/{runId}/listLogSasUrl Runs_GetLogSasUrl
POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/scheduleRun Registries_ScheduleRun
GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/tasks Tasks_List
DELETE /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/tasks/{taskName} Tasks_Delete
GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/tasks/{taskName} Tasks_Get
PATCH /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/tasks/{taskName} Tasks_Update
PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/tasks/{taskName} Tasks_Create
POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ContainerRegistry/registries/{registryName}/tasks/{taskName}/listDetails Tasks_GetDetails

Unauthenticated WireMock Cloud demo sandbox for Microsoft Azure — not an official Microsoft Azure sandbox, and it returns simulated example data only.

What's inside the registry-tasks template

ACR Tasks is the service that builds container images inside Azure instead of on your machine, and this template models its 2019-04-01 management surface. Fire a scheduleRun request and back comes a finished run resource named ca12 — the terse run-naming style the real service uses — flagged as a QuickBuild on Linux/amd64 with every lifecycle timestamp populated. Ask for its logs and the listLogSasUrl route responds the way Azure does: not log text, but a signed blob-storage link for fetching it.

  • Task definitions — create, update, list, and delete build tasks, plus the listDetails variant
  • Run lifecycle — schedule a run, then list, fetch, update, or cancel it
  • Build logs — the SAS-link route that stands between a run and its log stream
  • Source upload — listBuildSourceUploadUrl, the staging step before a context-tarball build

Frequently asked questions

Nothing is built — no worker spins up, no Dockerfile executes. What you get is the completed run resource, immediately, which is exactly what pipeline-orchestration code needs: the submit-poll-report loop can be tested in milliseconds instead of waiting out a genuine image build.

The link is shaped right — a blob URL with SAS query parameters — but it points at storage that doesn't exist, so dereferencing it fails. Test the parsing and expiry handling of the link itself; feed your log-tailing code from a private copy where you control a reachable URL.

Three templates slice ACR apart: the management template governs the registry resource, the data-plane template speaks to its contents, and this one owns the build subsystem in between. Keeping them separate keeps each mock small — combine their base URLs when a workflow spans the seams.

True, the sandbox never produces a broken build. Copy the template into WireMock Cloud and edit the run stubs: a status of Failed with a runErrorMessage, or a Queued run that never progresses, gives your retry and alerting logic the miserable cases it exists for.

Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.