Subdirectories are independent to each other, each represents a Terraform pattern of Azure Databricks workspace deployment.
Azure Databricks deployment patterns:
adb-exfiltration-protection, classic hub-spoke firewall setup for blog: https://databricks.com/blog/2020/03/27/data-exfiltration-protection-with-azure-databricks.html.adb-external-hive-metastore, Azure Databricks workspace with private endpoint connection to external hive metastore.adb-private-links, Azure Databricks workspace with multiple private links and firewall: Data Plane - Control Plane PL, Data Plane - DBFS PL.adb-with-squid-proxy, Azure Databricks workspace, with squid proxy to filter outbound traffic, decoupling data exfiltration costs from data volume.adb-service-endpoint-policy-experiment, an experimental setup with service endpoint policy, this setup is just for reference and trial using SEP. Granular egress outbound control through SEP is not directly supported.adb-trino-delta-connector, a POC setup to show Trino-Delta Connector.adb-splunk, a POC setup to show Splunk-Databricks connector, referring to https://github.com/databrickslabs/splunk-integration.adb-git-proxy, a reference implementation for Azure Databricks to connect to onprem Git server via a proxy cluster.