vuong-nguyen

@acshankar91 could you confirm whether this is an issue with terraform exporter?

@rahulgul could you make sure that the ADO runners have access to registry.terraform.io to download the necessary provider `could not query │ provider registry for registry.terraform.io/databricks/databricks: failed │ to retrieve...

@sveerella what happens when you re-run terraform plan? I notice that you are specifying `lifecycle {ignore_changes = all}`, which blocks any future drift detection

@JoshCadney this should have been fixed in the latest release - could you confirm that it is working now?

@ledbutter the only test I've seen that test this behaviour is `TestCatalogSuppressCaseSensitivity` under `catalog/resource_catalog_test.go`

> > @ledbutter the only test I've seen that test this behaviour is `TestCatalogSuppressCaseSensitivity` under `catalog/resource_catalog_test.go` > > Right, and this is so trivial I don't see much value in...

@david-tempelmann this is likely an issue with the backend, where grants acl are not taking effect immediately, i.e. eventual consistency.

@VOVELEE I suspect this is to do with how you are specifying the catalog in the `catalog_workspace_binding` - you should refer to a `databricks_catalog` attribute, rather than a var, otherwise...

@jesinity the issue with `force_update` and `skip_validation` is likely with the backend API, could you file a support ticket for this? the `client_secret` is not returned from the API, so...

@jesinity 1. If you can raise a support ticket for Azure Databricks, via Azure portal 2. I double-checked, `skip_validation` is supported for `databricks_external_location` but not for `databricks_storage_credential` - we will...