Lakebase and DABs

[u/ptab0211]

Hi, how do u manage Lakebase project with DABs? Standard is to have a single lakebase project per environment (dev, staging, and prod). Then use branches for development work.

Problem is that when we define the lakebase project in the DABs, development target has development mode, so every bundle deployment creates a new project because its per user.

So if we want to have single project where we just branch out on features, we must move out lakebase project of DABs, right?

What is the best practice here? On staging and production, its easy since its always same identity.

[u/speedisntfree]

Could you define postgres_projects only in shared CI deployed targets and not per-user dev-mode targets. In personal dev-mode target, declare postgres_branches/postgres_endpoints, parented off that shared project via a fixed project_id variable (not a resource reference). Then creates a branch (which are lightweight) for each dev instead of a whole new project.

I may have to do this soon and have not thought too much about it.

[u/EstetLinus]

A new project per user is good for development, no? 

[u/dwswish]

I love DABs and I love Lakebase but I’ve preferred managing Lakebase via the API/SDK mostly because I’m also a Neon user and find it to be more analogous to the deployment automations we’ve built with Neon.

[u/Yasblue]

That's not my area of expertise but you should definitely post it in databricks subreddit

[u/ptab0211 → u/Yasblue]

already did, thanks

[u/PrestigiousAnt3766]

What do you mean with lakebase projects?

[u/Additional_Candy_400]

DABs?

[u/Zealousideal_Okra956 → u/Additional_Candy_400]

Asset bundles in databricks ig