[ISSUE] Issue with databricks_system_schema resource

[Waiwait]

Configuration

databricks_system_schema resource passes silently when a schema has been disabled outside of terraform. This was discovered when we switched the metastore for a workspace and then dependent grants on the system_schema started failing after not finding the schema.

Expected Behavior

Terraform correctly recognises that the schema has been disabled outside of the state and acts appropriately.

Actual Behavior

Terraform silently passes, assuming that the schema is still enabled.

Steps to Reproduce

Terraform and provider versions

terraform-provider-databricks=1.49.0
terraform=v1.55.0

Is it a regression?

Debug Output

Important Factoids

Would you like to implement a fix?

I think this is caused by the Read function simply returning nil at the end of the for loop if no appropriate schema is found. This would be fixed by adding d.SetId("") to this, so that on the next run, it'll force a Create call. Happy to implement, just wanted to make sure this was the right approach.

[alexott]

yes, we're using similar approach in other resources, like, library: https://github.com/databricks/terraform-provider-databricks/blob/main/clusters/resource_library.go#L86