Microsoft.Kusto: Questions to the Permissions API design

[jrauschenbusch]

Why there is no dedicated RESTful sub-resource for Kusto Database permissions which uses a unique id like the subscription sub-resource of the service bus API?

Example:
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/servicebus/resource-manager/Microsoft.ServiceBus/stable/2017-04-01/servicebus.json#L2091

Current API:

POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}/databases/{databaseName}/addPrincipal

Suggested resource-based API:

PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Kusto/clusters/{clusterName}/databases/{databaseName}/permissions/{permissionId}

I think the only open point would be to define a meaningful id. But maybe this could be a generated UUID?

And why other properties than role and FQN are required? Imho these two properties would be sufficient to add a permission for a given principal.

[jrauschenbusch]

I think this is now solved with #7832.

Dedicated resources for ClusterPrincipalAssignment and DatabasePrincipalAssignment are available since Kusto API 2020-02-15.