docs(apps): recommend databricks apps deploy as the one-step deploy#164
Merged
Conversation
App-related skills now point at `databricks apps deploy` (validates, deploys, AND starts the app, returning its URL) instead of the bare `bundle deploy` + `bundle run` two-step. A plain `bundle deploy` creates the app with `no_compute` and leaves it stopped, which led agent runs to emit a separate manual start step. The bundle commands stay documented as an advanced/bundle-native fallback, and the `bundle deploy`-leaves-it-stopped behavior is now stated once so the reason is clear. Co-authored-by: Isaac
c850b8b to
83418f0
Compare
atilafassina
approved these changes
Jun 19, 2026
simonfaltum
approved these changes
Jun 19, 2026
simonfaltum
added a commit
that referenced
this pull request
Jun 19, 2026
PR #164 edited four databricks-apps / databricks-dabs source files after this branch was cut, so the committed per-provider bundle copies drifted (CI validate caught it on the merge checkout). Merge main and regenerate so all four providers' skill copies match the updated source. Also remove the now-dead `.codex-plugin/**` trigger from validate-manifest.yml: this PR moved Codex's plugin.json into plugins/databricks/codex/.codex-plugin/ (already covered by `plugins/**`), so root `.codex-plugin/` no longer exists. Co-authored-by: Isaac Signed-off-by: simon <simon.faltum@databricks.com>
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.
What
For all app-related skills, recommend the single
databricks apps deploycommand instead of the barebundle deploy+bundle runtwo-step.databricks apps deployvalidates, deploys, and starts the app (returning its URL) in one step. A plaindatabricks bundle deploycreates the app withno_computeand leaves it stopped — which is why agent runs were emitting a separate manual start step (e.g. "To start the deployed app: rundatabricks apps start …"). The bundle commands stay documented as an advanced/bundle-native fallback, and the "deploy leaves it stopped" reason is now stated once.Why
Follows up on the Slack discussion about why deploying an app took two CLI steps. Confirmed in the CLI source:
bundle deployusesno_compute=true;apps deployruns the app; andlifecycle.started: true(databricks/cli#4672) flipsno_computeoff. The companion appkit PR bakeslifecycle.started: trueinto the scaffolding template so any deploy path leaves the app running.Changes
skills/databricks-apps/references/platform-guide.md— Deployment Workflow now leads withapps deploy; the bundle two-step is an advanced note; Common Errors row updated.skills/databricks-apps/references/other-frameworks.md— Critical Rules +config:note recommendapps deploy.skills/databricks-dabs/references/deploy-and-run.md— app-scoped "App not starting after deploy" row points atapps deploy(generic job/pipeline guidance untouched).skills/databricks-apps/SKILL.md— note theurlfield fromapps get.python3 scripts/skills.py validatepasses (docs-only; no manifest/metadata drift).This pull request and its description were written by Isaac.