Azure Datalake Store Account
Connector for the azure-datalake-store-account 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
oauthcredential. Mint one withitcli.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
operations_list— GET /providers/Microsoft.DataLakeStore/operations — Lists all of the available Data Lake Store REST API operations.accounts_list— GET /subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/accounts — Lists the Data Lake Store accounts within the subscription. The response includelocations_getcapability— GET /subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/locations/{location}/capability — Gets subscription-level properties and limits for Data Lake Store specified by rlocations_getusage— GET /subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/locations/{location}/usages — Gets the current usage count and the limit for the resources of the location undaccounts_listbyresourcegroup— GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeStore/accounts — Lists the Data Lake Store accounts within a specific resource group. The responsaccounts_get— GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeStore/accounts/{accountName} — Gets the specified Data Lake Store account.
Inputs
- a linked
oauthcredential (no key inputs) — the server injects a freshAuthorization: Bearerfrom it operation— one of the operations above- path parameters when an operation's path contains
{...} query— optional JSON object of query paramsbody— JSON object for create/update ops
Example
operation: operations_list
# (attach an 'oauth' credential to the task — no inline secrets)