Azure Devtestlabs Dtl

Connector for the azure-devtestlabs-dtl API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://management.azure.com
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• provideroperations_list — GET /providers/Microsoft.DevTestLab/operations — Result of the request to list REST API operations
• labs_listbysubscription — GET /subscriptions/{subscriptionId}/providers/Microsoft.DevTestLab/labs — List labs in a subscription.
• operations_get — GET /subscriptions/{subscriptionId}/providers/Microsoft.DevTestLab/locations/{locationName}/operations/{name} — Get operation.
• globalschedules_listbysubscription — GET /subscriptions/{subscriptionId}/providers/Microsoft.DevTestLab/schedules — List schedules in a subscription.
• labs_listbyresourcegroup — GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevTestLab/labs — List labs in a resource group.
• artifactsources_list — GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevTestLab/labs/{labName}/artifactsources — List artifact sources in a given lab.

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: provideroperations_list
# (attach an 'oauth' credential to the task — no inline secrets)