ghost
commented
1 year ago Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @arindamc.
Issue Details
We wish to enable admin protection for "no-isolation shared" clusters via the API ([see here for MS docs](https://learn.microsoft.com/en-gb/azure/databricks/administration-guide/account-settings/no-isolation-shared)), so that it can be enabled downstream in Terraform. Microsoft just added this parameter to their list of security advisory flags, so now our databricks instances are considered insecure by our internal IT department unless this flag is switched on. Given that many (including us) provision databricks via API, it is important that we are able to enable this flag when creating a Databricks resource. Related tickets: https://github.com/hashicorp/terraform-provider-azurerm/issues/18881 and https://github.com/databricks/terraform-provider-databricks/issues/1680 Thank you!
| Author: | dvasdekis |
|---|---|
| Assignees: | - |
| Labels: | `Service Attention`, `customer-reported`, `Data Bricks`, `feature-request` |
| Milestone: | - |
navba-MSFT
dvasdekis
We wish to enable admin protection for "no-isolation shared" clusters via the API (see here for MS docs), so that it can be enabled downstream in Terraform.
Microsoft just added this parameter to their list of security advisory flags, so now our databricks instances are considered insecure by our internal IT department unless this flag is switched on.
Given that many (including us) provision databricks via API, it is important that we are able to enable this flag when creating a Databricks resource.
Related tickets: https://github.com/hashicorp/terraform-provider-azurerm/issues/18881 and https://github.com/databricks/terraform-provider-databricks/issues/1680
Thank you!