[draft] skills: split out databricks-app-resources; add Lakebase session-branch isolation#184
Open
bernardo-rodriguez wants to merge 1 commit into
Conversation
…ch isolation Split app-side resource flows — app-vs-space levels, `apps create-update` merge semantics, scaffold-time wiring, and the deployed-app service-principal ownership / deploy-first model — into a new databricks-app-resources skill, and slim databricks-lakebase to the Lakebase-specific details those flows pull. Add session-branch isolation guidance to databricks-lakebase's app-resource section: suggest a dev branch off `production` and ask up front, then attach the resource -> fork the branch -> register, in that order, so the branch inherits the app service principal's role (never hand-create roles or grants). Co-authored-by: Isaac
bernardo-rodriguez
requested review from
a team,
lennartkats-db and
simonfaltum
as code owners
bernardo-rodriguez
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two related changes:
New
databricks-app-resourcesskill — split app-side resource flows out ofdatabricks-lakebase: app-vs-space resource levels,apps create-update(read-merge-submit /update_masksemantics), scaffold-time wiring, the deployed-app service-principal ownership / deploy-first model, and consent.databricks-lakebaseis slimmed to Lakebase-specifics and points here for the app-side flows.Lakebase session-branch isolation (
databricks-lakebase) — when setting up Lakebase for an app, suggest iterating on a copy-on-write branch offproductionand ask up front. On go-ahead: attach the resource → fork the branch → register, in that order, so the branch inherits the app service principal's Postgres role (forking first fails with28P01; never hand-create roles or grants).Why
Backs the App Builder Lakebase session-branch isolation feature (universe#2128750): a builder session iterates on an isolated branch while deploy keeps using the app's bound branch. The guidance lives in the shared skill so both Claude Code and the hosted builder follow the same flow.
This pull request and its description were written by Isaac.