We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
databricks_workspace_binding
resource "databricks_external_location" "checkpointing" { name = "${var.environment}_${azurerm_storage_container.checkpointing.name}" url = "abfss://${azurerm_storage_container.checkpointing.name}@${azurerm_storage_account.datalake.name}.dfs.core.windows.net/" credential_name = databricks_storage_credential.datalake_storage_account.name comment = "Managed by TF" isolation_mode = "ISOLATED" force_destroy = true force_update = true } resource "databricks_workspace_binding" "checkpointing" { workspace_id = azurerm_databricks_workspace.databricks_workspace.workspace_id securable_name = databricks_external_location.checkpointing.name securable_type = "external-location" }
The two resources are destroyed successfully
│ Error: cannot delete external location: External Location '***' is not accessible in current workspace
Because of this behavior, tearing down related resources can only be done with workaround/manual intervention
The text was updated successfully, but these errors were encountered:
I'm having this problem also. Any updates? I found this related issue: #4305
Sorry, something went wrong.
No branches or pull requests
Configuration
Expected Behavior
The two resources are destroyed successfully
Actual Behavior
│ Error: cannot delete external location: External Location '***' is not accessible in current workspace
Because of this behavior, tearing down related resources can only be done with workaround/manual intervention
Steps to Reproduce
The text was updated successfully, but these errors were encountered: