Hmm it seems that Databricks developers say that creating tables/views in Unity Catalog from TerraForm is discouraged:

> so there are quite a few gaps/edge cases with the tables API, hence customers should not use the API or Terraform to create/manage Unity Catalog tables & views at the moment.

So then I think the best way to create tables/views is via a Job, until such time that Databricks offers a stable API to do this via Terraform.

For posterity, there's also another way to communicate data from TF to Databricks: via K8s secrets.