Open amwill04 opened 2 hours ago
resource "databricks_metastore_data_access" "this" { metastore_id = databricks_metastore.this.id name = aws_iam_role.metastore_data_access.name aws_iam_role { role_arn = aws_iam_role.metastore_data_access.arn } is_default = true }
Running terraform apply multiple times does not end up with the field value is_default causing the resource to be replaced
terraform apply
is_default
The fact that the field storage_root_credentials_name is not being returned the following always resolves to false here
storage_root_credentials_name
false
run `terraform apply multiple times even without any changes
terraform v1.9.5 databricks 1.9.3
terraform v1.9.5
databricks 1.9.3
Seems to have suddenly started . However this could potentially have been caused by changes in the sdk that this uses?
sdk
Further to note - I could not replicate this on a newly created metastore within a different AWS region. This metastore was created over a year ago
metastore
Configuration
Expected Behavior
Running
terraform apply
multiple times does not end up with the field valueis_default
causing the resource to be replacedActual Behavior
The fact that the field
storage_root_credentials_name
is not being returned the following always resolves tofalse
hereSteps to Reproduce
run `terraform apply multiple times even without any changes
Terraform and provider versions
terraform v1.9.5
databricks 1.9.3
Is it a regression?
Seems to have suddenly started . However this could potentially have been caused by changes in the
sdk
that this uses?