Microsoft Azure HDInsightManagementClient

What authentication does this API use?

It uses Azure AD OAuth2 against management.azure.com, declared as the azure_auth security scheme. Through Jentic, your service principal credentials sit in the encrypted vault and are exchanged for a scoped bearer token at execution time.

Does this API let me create a cluster?

No. This 2018-06-01-preview surface is scoped to cluster applications only - install, list, get, and delete add-on workloads on an existing cluster. To provision the cluster itself, use a more recent HDInsight Management API or ARM template that exposes the clusters resource.

What are the rate limits?

Standard ARM throttles apply at the subscription level - about 12,000 reads and 1,200 writes per hour per subscription. PUT and DELETE on applications are long-running, so callers should poll the Azure-AsyncOperation header rather than retry the original request.

How do I install a cluster application through Jentic?

Run jentic.search('install an application on an hdinsight cluster'), load the Applications_Create schema, and execute it with the subscription, resource group, cluster name, application name, and the application definition body. The PUT returns 202 and the async operation reports success once installation completes.

Can I limit what my agent is allowed to do with the Azure HDInsight Management API?

Yes. Because you run Jentic One yourself, your own rules decide which of the four Applications operations your agent may call, so you can allow listing and reading cluster applications while withholding install (PUT) and delete unless you grant them. Since the cluster and application names travel in the URL path under /clusters/{clusterName}/applications/{applicationName}, a rule can pin the agent to named clusters and named applications. The Azure service principal credentials stay in your own instance and are exchanged for a scoped bearer token at execution time, so the agent only ever calls the operations you have approved.