Skip to content
All topics

Terraform Provider

Recent items mentioning Terraform Provider across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.

43 recent items38 releases4 videos1 community thread
What's happening in Terraform ProviderAI synthesis · updated 3d ago

New databricks_domain and databricks_sandbox resources have landed alongside secret securable support in databricks_grant 6 and write-only value attributes (string_value_wo) in databricks_secret 1. Meanwhile, practitioners are actively re-evaluating where to draw the boundary between Terraform and Databricks Asset Bundles now that bundles' direct engine is the default deployment mechanism 4.

Generated daily from the 8 most recent items mentioning Terraform Provider. Click any [N] to jump to the source.

Reddit

Now that direct engine is the default, where are you drawing the line between bundles and the Terraform provider?

Moved our bundles off the Terraform engine a while back. bundle deployment migrate , tfstate turns into resources.json, plan came back clean, deploys are noticeably quicker. No complaints about the migration itself. What I haven't settled is scope. The old split was easy. Terraform provider owned the platform — workspaces, metastore, groups, catalogs, external locations, policies. Bundles owned what the data team ships — jobs, pipelines, a couple of schemas. Now bundles do catalogs, external locations, cluster policies and grants, several of them only on the direct engine, so the provider isn't the only path to UC-as-code anymore. Which leaves me with two state files describing overlapping resource types, and "who owns this catalog" has quietly become a team boundary question instead of a technical one. Where I've landed for now: anything account-scoped or shared across workspaces stays in Terraform, anything whose lifecycle matches a git repo goes in the bundle. Grants are the annoying case, they sit right on the seam. One thing that did bite us. The direct engine reverts removed fields to defaults, where the Terraform engine used to leave the previous value in place. Deleting a line from databricks.yml is now a real change. Caught it in a plan, but it's a different mental model and I don't think it's widely understood yet. How are you splitting it? Provider for everything platform-side, or have you pulled the UC objects into bundles and just accepted living with two state files? submitted by /u/AbilyticsEng [link] [comments]

00AbilyticsEng1w ago

Get Tuesday's version of this

Tracking Terraform Provider? The Tuesday email carries what moved across the whole ecosystem, not just this topic. Free, one-click unsubscribe.

Read past issues first