Open jrauschenbusch opened 4 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @radennis.
Adding @ilayrn
@jrauschenbusch Thanks for reaching out! Currently language extension is not cluster property and could be configured only post cluster creation (with POST operation). Supporting language extension as cluster property (and thus, could be configured in PUT operation) is in our road map but there is no ETA yet.
@orhasban Thanks for the response. Please let me know when it‘s available. Would simplify things a lot within the terraform provider.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ilayrn, @orhasban, @astauben.
Specified language extensions (PYTHON, R) are not considered during a Kusto Cluster PUT operation using the
azure-sdk-for-go
client.Used client: https://github.com/Azure/azure-sdk-for-go/blob/master/services/kusto/mgmt/2020-02-15/kusto
PUT specification: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2020-02-15/kusto.json#L59
Language extensions are not read-only property, hence they should be usable within a PUT: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/azure-kusto/resource-manager/Microsoft.Kusto/stable/2020-02-15/kusto.json#L2514
Expected behavior: Cluster is created and selected language extensions are enabled during PUT operation.
Actual behavior: Cluster is created, but language extensions won't be activated.