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.

47 recent items41 releases4 videos2 community threads
What's happening in Terraform ProviderAI synthesis · updated 11d ago

The Databricks Terraform provider removed all Mason resources following an underlying API rename to AgentKit, alongside removals of feature engineering Kafka configurations and materialized feature resources 1. Earlier updates introduced write-only secret attributes 5, enabled schema-level connection management 4, and expanded resource exporter support to include Databricks Apps, model serving endpoints, and Lakeflow pipeline settings 3.

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

Reddit

Terraform provider for Dataiku DSS

Dataiku has no official Terraform provider, so I wrote one. It manages what lives inside a running DSS instance: projects, users, groups, connections, code environments, scenarios, project permissions and variables, and the containerized execution settings. resource "dataiku_group" "data_scientists" { name = "data_scientists" description = "Analysts who build and run models" } resource "dataiku_project" "analytics" { project_key = "ANALYTICS" name = "Analytics" owner = "admin" tags = ["managed-by-terraform"] } resource "dataiku_project_permissions" "analytics" { project_key = dataiku_project.analytics.project_key permission { group = dataiku_group.data_scientists.name read_project_content = true write_project_content = true run_scenarios = true } } Every resource supports import, so the way in on an instance that already matters is to import what's there and read the plan before letting Terraform change anything. It's 0.x, so pin a minor version. Two limits are licensing rather than gaps in the provider: scenario temporal triggers, and actually running containerized execution. Writing the container settings works anywhere, but running a recipe in a container needs the licence for it. If you have no DSS to point it at, there's a docker compose in the repo for a throwaway one. Registry: https://registry.terraform.io/providers/amrutp24/dataiku/latest Source: https://github.com/amrutp24/terraform-provider-dataiku It's mine, nothing is for sale. Two things I'd like to hear: whether a plan against your own instance wants to change something you didn't expect, and which missing resource is the one that stops you using it. submitted by /u/apagidip [link] [comments]

00apagidip1w ago
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]

00AbilyticsEng1mo ago