terraform-databricks-examples
terraform-databricks-examples copied to clipboard
Examples of using Terraform to deploy Databricks resources
Make [adb-with-private-links-exfiltration-protection](https://github.com/databricks/terraform-databricks-examples/tree/main/examples/adb-with-private-links-exfiltration-protection) matching the [blog](https://www.databricks.com/blog/data-exfiltration-protection-with-azure-databricks)
Using a provider of ``` provider "databricks" { profile = "ACCOUNT-" } ``` This doesn't create: ``` resource "databricks_mws_workspaces" "this" { provider = databricks account_id = var.databricks_account_id aws_region = var.region...
I.e., this could affect us: - https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#specifying-subscription-id-is-now-mandatory - https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#azurerm_databricks_workspace_customer_managed_key - https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#azurerm_databricks_workspace
Historically, the external ID was well-known (the account ID) when storage credentials were created by account admins. Now that storage credentials can be created by non-admins, we want to show...
@alexott Configuration resource "databricks_metastore_data_access" "first" { provider = databricks.workspace metastore_id = databricks_metastore.this.id name = "${var.storage_credential_name}-root" azure_managed_identity { access_connector_id = azurerm_databricks_access_connector.unity.id } is_default = true depends_on = [databricks_metastore_assignment.this] } Expected Behavior...
Revamping this example of modular AWS DB workspace deployment - we can now define multiple environments with yaml files to deploy **m** workspaces into **n** VPCs and create multiple catalogs...
To make overhaul change and update this example that deploys multiple aws databricks workspaces. Also change the current hard coded configs to config file driven (yaml) deployment. We should be...
The module still uses the CMv2 architecture. When the CMv1 architecture will be released and supported by Terraform provider, the implementation will be reviewed
When I use all 3 GCP examples in the repo I have an error: │ Error: cannot create mws networks: failed during request visitor: inner token: impersonate: status code 403:...
The new workspace architecture on GCP isn't based on GKE anymore and has a bit different network requirements. The Databricks TF provider 1.71 is released with support for new network...