feat(appkit): support Lakebase Autoscaling x Apps integration natively#132
Draft
feat(appkit): support Lakebase Autoscaling x Apps integration natively#132
Conversation
f481ccb to
9fc9700
Compare
f1c11f3 to
d422879
Compare
8e4e80e to
5a02a65
Compare
573be52 to
fad99ea
Compare
| "description": "Lakebase Postgres database for persistent storage", | ||
| "permission": "CAN_CONNECT_AND_CREATE", | ||
| "fields": { | ||
| "name": { |
Collaborator
There was a problem hiding this comment.
this is the only thing we have to collect for lakebase v2? no branch, or project or anything else? just the endpoint?
Member
Author
There was a problem hiding this comment.
actually now we don't need anything at all 😄 no envs, because PGENDPOINT is automatically injected
and for DABs we'll need branch + database paths - that's something CLI will pass from the interactive selection 👍
39d84e8 to
df78895
Compare
fad99ea to
c7b3325
Compare
df78895 to
39f8d94
Compare
c7b3325 to
6daae12
Compare
39f8d94 to
8877ac5
Compare
github-merge-queue bot
pushed a commit
to databricks/cli
that referenced
this pull request
Feb 27, 2026
…y files after template rendering (#4549) ## Changes - Show setup notes for plugins which have such instructions (needed for Lakebase plugin temporarily) - Remove hardcoded paths for analytics plugin - this will be handled purely by Go templates in the template itself - Remove empty files and directories after template rendering - Setup listers for `postgres` resource - ~Run "postinit" npm command in context of template if it exists~ - reverted as we don't need it for now Those changes need to be synchronized with AppKit where we add the `templatePaths` property in the manifest. ## Why - We're introducing new plugins, and depending on them, we need to configure the dynamic template. The hardcoded solution is not scalable, as I pointed out here: #4469 (comment) See also https://databricks.atlassian.net/browse/LKB-9681 ## Screenshot <img width="1461" height="738" alt="image" src="https://github.com/user-attachments/assets/966f8f84-94a4-4d4a-856e-7f5cdc703a57" /> ## Demo (just the listers for future Lakebase plugin changes databricks/appkit#132) https://github.com/user-attachments/assets/c745baad-662b-4f82-b197-ed95fcb89ef7
059d965 to
5dc9f6f
Compare
6daae12 to
6420b2f
Compare
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
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.
LAKEBASE_ENDPOINTtoPGENDPOINT- it is automatically injected by AppsWill be tested on stage, and merged once the integration is live on production.
Video
Screen.Recording.2026-02-24.at.15.43.45.mov