Closed sebastienroy-accelex closed 10 months ago
We are also having this same issue
We are also having this issue on 1.33.0
Thanks for raising. Are you using your AWS account ID in the account_id
field of databricks_mws_credentials
? You should be providing the E2 account ID there.
There was a bug with this in 1.31.0, but it was fixed in 1.32.0. To be 100% sure, you can try specifying the account ID in the provider
block as opposed to in the databricks_mws_credentials
resource.
Thanks for raising. Are you using your AWS account ID in the
account_id
field ofdatabricks_mws_credentials
? You should be providing the E2 account ID there.There was a bug with this in 1.31.0, but it was fixed in 1.32.0. To be 100% sure, you can try specifying the account ID in the
provider
block as opposed to in thedatabricks_mws_credentials
resource.
Another commenter suggested moving the account_id
under provider
and this resolved the issue for us. Thanks.
Thanks for raising. Are you using your AWS account ID in the
account_id
field ofdatabricks_mws_credentials
? You should be providing the E2 account ID there.There was a bug with this in 1.31.0, but it was fixed in 1.32.0. To be 100% sure, you can try specifying the account ID in the
provider
block as opposed to in thedatabricks_mws_credentials
resource.
Hi @mgyucht .
This is a wrong copy paste in my comment. I tried to make it simple but I actually made it more confusing.
I updated the comment with a random ID. I also confirm I use E2 account ID for account_id
.
Having same error here:
2024-01-15T13:40:37.670-0300 [ERROR] vertex "databricks_mws_credentials.databricks-e2-workspaces-1" error: cannot read mws credentials: invalid Databricks Account configuration
2024-01-15T13:40:37.670-0300 [ERROR] vertex "databricks_mws_credentials.databricks-e2-workspaces-1" error: cannot read mws credentials: invalid Databricks Account configuration
2024-01-15T13:40:37.670-0300 [ERROR] provider.terraform-provider-databricks_v1.34.0: Response contains error diagnostic: tf_provider_addr=registry.terraform.io/databricks/databricks @caller=/home/runner/work/terraform-provider-databricks/terraform-provider-databricks/vendor/github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/diag/diagnostics.go:62 @module=sdk.proto diagnostic_detail= diagnostic_severity=ERROR tf_proto_version=5.4 tf_req_id=1f286ea3-9294-82ca-2b1e-3f91668dcf8c tf_resource_type=databricks_mws_credentials tf_rpc=ReadResource diagnostic_summary="cannot read mws credentials: invalid Databricks Account configuration" timestamp=2024-01-15T13:40:37.670-0300
2024-01-15T13:40:37.670-0300 [ERROR] vertex "databricks_mws_credentials.databricks-e2-workspaces-1 (expand)" error: cannot read mws credentials: invalid Databricks Account configuration
Moving account_id
to provider section fixes it.
Thanks @waldman @VPAI-Bixal !
Moving account_id
to provider section fixed it for me. I am now able to use version 1.34.0
.
Hi team
Terraform and provider versions
Is it a regression?
Yes, everything run fine with version
1.31.0
. Broken with newer versions (>=1.31.1).Configuration
Error
Error: cannot read mws credentials: invalid Databricks Account configuration
Debug Output
Providing only the relevant lines.