@Daniel Bedrenko​ :

Yes, you are correct. The Databricks developers discourage using the API or Terraform to create and manage Unity Catalog tables and views due to gaps and edge cases with the tables API. Instead, they recommend using Jobs to create and manage tables and views.

Using Jobs is a good alternative to using Terraform to create tables and views. You can create a Job with a script that creates tables or views, and then use Terraform to manage the Job. This allows you to create and manage tables and views from Terraform while avoiding the gaps and edge cases of the tables API.

Regarding the communication of data from Terraform to Databricks, using Kubernetes secrets is a good option. You can create a Kubernetes secret with the configuration data that needs to be used in the Databricks workspace, and then pass the secret to your Databricks cluster as an environment variable or a mounted volume.

Overall, using Jobs and Kubernetes secrets are good solutions to create and manage tables and views in the Unity Catalog from Terraform and communicate data from Terraform to Databricks.