hashicorp / terraform-provider-azurerm

Terraform provider for Azure Resource Manager
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs
Mozilla Public License 2.0
4.46k stars 4.54k forks source link

Support for Azure Databricks Workspace Enhanced Security & Compliance #25700

Open zogamorph opened 2 months ago

zogamorph commented 2 months ago

Is there an existing issue for this?

Community Note

Description

The azurerm_databricks_workspace to support the enhanced security compliance options for azure. The follow options are

New or Affected Resource(s)/Data Source(s)

azurerm_databricks_workspace

Potential Terraform Configuration

resource "azurerm_databricks_workspace" "myDataBricksWorkspave" {
    name                                                = "dbw-myworkspave-dev"
    resource_group_name                                 = "rg-dbw-dev"
    location                                            = "uksouth"
    sku                                                 = "premium"

    custom_parameters {
      no_public_ip                                         = true
      private_subnet_name                                  = "sub-dbw-private-dev"
      public_subnet_name                                   = "sub-dbw-public-dev"
      virtual_network_id                                   = "/resourceGroups/rg-network-dev/providers/Microsoft.Network/virtualNetworks/vnet-myvnet-DEV"
    }

   enhanced_security_compliance {
          automatic_cluster_Update = true          
          enhancedSecurityMonitoring = true          
          compliance_securit_profile  {
              complianceStandards = ["HIPAA", "PCI_DSS"]
          }
  }

References

This show how to apply the changes via the ARM template: https://learn.microsoft.com/en-us/azure/databricks/security/privacy/enhanced-security-compliance#--use-an-arm-template

snacks-lord commented 2 days ago

This would be extremely helpful. Currently the only option in Azure is to go into the portal to enable these (after the workspace is created). image

ssouthcity commented 1 day ago

Once enabled in the GUI the Azure API expects these options to be sent with every subsequent update request, which breaks the functionality of our CI/CD pipelines. I have began work on this issue in my own fork of the repo :)