---
title: "Discussion on \"Terraform & Databricks CI/CD Part 3: The Design Decisions Behind the Job Layer\" | Hashnode"
description: "Discussion on \"Terraform & Databricks CI/CD Part 3: The Design Decisions Behind the Job Layer\". Where We Left Off\nPart 1 of this series stood up the Azure infrastructure and Databricks workspace via Terraform. Part 2 added the Unity Catalog layer — catalog, schemas, and grants — managed through"
url: "https://hashnode.com/posts/terraform-databricks-ci-cd-part-3-the-design-decisions-behind-the-job-layer/69b7c69e51ec0ee7bc09c679"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Terraform & Databricks CI/CD Part 3: The Design Decisions Behind the Job Layer](https://platform-notes.hashnode.dev/terraform-databricks-ci-cd-part-3-the-design-decisions-behind-the-job-layer?utm_source=hashnode&utm_medium=feed)

Where We Left Off Part 1 of this series stood up the Azure infrastructure and Databricks workspace via Terraform. Part 2 added the Unity Catalog layer — catalog, schemas, and grants — managed through

Mar 16 · 20 min read · platform-notes.hashnode.dev  
Read the article

-   [#databricks](https://hashnode.com/tag/databricks)
-   [#azure](https://hashnode.com/tag/azure)
-   [#terraform](https://hashnode.com/tag/terraform)
-   [#databricks-asset-bundles](https://hashnode.com/tag/databricks-asset-bundles)
-   [#pyspark](https://hashnode.com/tag/pyspark)
-   [#ci-cd](https://hashnode.com/tag/ci-cd)

## Written by

[nobhri](https://hashnode.com/@nobhri)

@nobhri · Yokohama, Japan

  
[View profile](https://hashnode.com/@nobhri)

Data Platform Architect · Azure · Databricks · Unity Catalog

Data Platform Engineer / de-facto Architect at a large manufacturing company. Building enterprise-grade Databricks platforms on Azure under real organizational constraints. Writing about governance design, IaC, and architectural decision-making.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
