Skip to content
Cloud infrastructure/devops

azure.com:devops

Azure DevOps sandbox and mock API

Azure DevOps Resource Provider Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
8
Collections
-
Event types
-
example request
curl https://your-azure-devops.slurry.io/providers/Microsoft.DevOps/operations \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2019-07-01-preview.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

All 8.

  • GET/providers/Microsoft.DevOps/operations
  • GET/providers/Microsoft.DevOps/pipelineTemplateDefinitions
  • GET/subscriptions/{subscriptionId}/providers/Microsoft.DevOps/pipelines
  • GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines
  • GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
  • PUT/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
  • PATCH/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
  • DELETE/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}