feat(template): auto-start apps on deploy via lifecycle.started#454
Merged
Conversation
Add `lifecycle.started: true` to the scaffolded `databricks.yml` so a deploy leaves the app running and returns its URL, with no separate start step. Update the template README to use the single `databricks apps deploy` command instead of the `bundle deploy` + `bundle run` two-step. Resolves the friction where a scaffolded app required a manual `bundle run` / `apps start` after deploy. Co-authored-by: Isaac
pkosiec
force-pushed
the
pkosiec/update-bundle
branch
from
5de79b7 to
57607da
Compare
MarioCadenas
approved these changes
Jun 19, 2026
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
2 participants
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
lifecycle.started: trueto the scaffoldedtemplate/databricks.yml.tmpl(underresources.apps.app), so a deploy starts the app and returns its URL — no separate start step.template/README.mddeployment section to use the singledatabricks apps deploycommand instead of thebundle validate→bundle deploy→bundle runsequence. Adds a short note on restarting a stopped app withdatabricks apps start.Why
A bare
databricks bundle deploycreates the app withno_compute=trueand leaves it stopped, so the scaffolded two-step README (bundle deploythenbundle run) was the source of agent runs emitting a manual trailing start step (e.g. "To start the deployed app: rundatabricks apps start …").lifecycle.started: true(databricks/cli#4672) flipsno_computeoff; it's supported in direct deployment mode, which is the CLI default. The companion agent-skills PR aligns the docs to recommenddatabricks apps deploy.Notes
lifecycle.startedrequires direct deployment mode (CLI default); only explicit terraform mode (DATABRICKS_BUNDLE_ENGINE=terraform) rejects it. Requires Databricks CLI ≥ v0.297.0.cc the appkit maintainers for review.
This pull request and its description were written by Isaac.