Kusto returns Terminal rather than Failed

[tombuildsstuff]

👋

When provisioning a Kusto Cluster via our Test Suite - we've noticed an error being returned from the API:

Code="RequestConflict"
Message="Cannot modify resource with id '/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/acctestRG-191216063251381036/providers/Microsoft.Kusto/Clusters/acctestkcdluqfx' because the resource entity provisioning state is not terminal. Please wait for the provisioning state to become terminal and then retry the request."

Every other Azure API I'm aware of returns resources which have finished provisioning with an error as Failed - however it appears that the Kusto API returns this as terminal. Would it be possible to get this fixed so that downstream clients can handle the cases appropriately?

Thanks!

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @radennis.

[radennis]

From the error it seems you are trying to perform an operation on a cluster resource which still hasn't finished a previous operation. Kusto does return a terminal operation once it finishes the operation

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ilayrn, @orhasban, @astauben.