Inconsistent `storage_root` Value During Apply Causes Provider Plan Error (Databricks Provider)

[haleyyyblue]

Summary

When applying a Terraform configuration using the databricks provider, the plan phase completes successfully, but during the apply phase, the provider returns an inconsistent final plan error due to a discrepancy in the storage_root value.

Error Message

│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for
│ module.sandbox_environment.databricks_catalog.uc_quickstart to include new
│ values learned so far during apply, provider
│ "registry.terraform.io/databricks/databricks" produced an invalid new value
│ for .storage_root: was cty.StringVal("s3://uc-quickstart-c6pv7v-sandbox"),
│ but now cty.StringVal("s3://uc-quickstart-c6pv7v-sandbox/").
│
│ This is a bug in the provider, which should be reported in the provider's own
│ issue tracker.

Expected Behavior

The apply step should complete successfully without requiring multiple executions or causing final plan consistency errors.

Actual Behavior

The initial terraform apply fails due to a mismatch between the expected and the actual storage_root value. The only difference is the presence or absence of a trailing slash (/). Interestingly, rerunning terraform apply completes successfully, indicating the state stabilizes after the first failure.

Steps to Reproduce

1. Define a Databricks catalog using a storage_root similar to:
   s3://uc-quickstart-<workspace-suffix>-sandbox
2. Run terraform apply
3. Observe the error regarding inconsistent plan state due to trailing slash.
4. Run terraform apply again – it completes without error.

Workaround

A second execution of terraform apply resolves the issue temporarily.

Terraform Version

Terraform v1.8.2