Closed crankswagon closed 10 months ago
Commenting that we are seeing this issue as well. Works on 1.31.0
breaks on 1.31.1
.
This is affecting us too.
This is effecting us too
We are seeing this problem too. We rolled back to v1.31.0
for the time being.
This is addressed in https://github.com/databricks/terraform-provider-databricks/pull/3028. We plan to release the provider with this fix by EOD tomorrow. I will close this issue as there is no work to be done, and you can update to the release with this fix (will be 1.32.0) once it is available.
Bumped to version 1.32.0
, still getting exactly same error, as in version 1.31.1
.
Additionally, same error if optional account_id
is removed from databricks_mws_credentials
as mentioned in https://github.com/databricks/terraform-provider-databricks/pull/3028#pullrequestreview-1781557910.
We are still seeing the issue on 1.33.0
I was able to update successfully to 1.33.0
after these changes:
account_id
is removed from all databricks_mws_credentials
resourcesaccount_id
is set in provider:
provider "databricks" {
alias = "mws"
host = "https://accounts.cloud.databricks.com"
account_id = var.databricks_account_id
// ...
}
I was able to update successfully to
1.33.0
after these changes:* optional `account_id` is removed from all `databricks_mws_credentials` resources * `account_id` is set in provider:
provider "databricks" { alias = "mws" host = "https://accounts.cloud.databricks.com" account_id = var.databricks_account_id // ... }
So far this seems to be working for us, thanks!
databricks_mws_credentials
using account level provider configured with username + password auth failing in new version.Configuration
Expected Behavior
Applies as per normal
Actual Behavior
Failed with invalid account error when using provider version
1.31.1
Steps to Reproduce
terraform plan
Terraform and provider versions
Works with
1.31.0
Fails with1.31.1
Is it a regression?
Yes; last worked with
1.31.0
Debug Output
Possibly due to Go SDK refactor in new version