Skip to content

docs(apps): recommend databricks apps deploy as the one-step deploy#164

Merged
pkosiec merged 1 commit into
mainfrom
pkosiec/apps-deploy
Jun 19, 2026
Merged

docs(apps): recommend databricks apps deploy as the one-step deploy#164
pkosiec merged 1 commit into
mainfrom
pkosiec/apps-deploy

Conversation

@pkosiec

@pkosiec pkosiec commented Jun 19, 2026

Copy link
Copy Markdown
Member

What

For all app-related skills, recommend the single databricks apps deploy command instead of the bare bundle deploy + bundle run two-step.

databricks apps deploy validates, deploys, and starts the app (returning its URL) in one step. A plain databricks bundle deploy creates the app with no_compute and leaves it stopped — which is why agent runs were emitting a separate manual start step (e.g. "To start the deployed app: run databricks 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 deploy uses no_compute=true; apps deploy runs the app; and lifecycle.started: true (databricks/cli#4672) flips no_compute off. The companion appkit PR bakes lifecycle.started: true into the scaffolding template so any deploy path leaves the app running.

Changes

  • skills/databricks-apps/references/platform-guide.md — Deployment Workflow now leads with apps deploy; the bundle two-step is an advanced note; Common Errors row updated.
  • skills/databricks-apps/references/other-frameworks.md — Critical Rules + config: note recommend apps deploy.
  • skills/databricks-dabs/references/deploy-and-run.md — app-scoped "App not starting after deploy" row points at apps deploy (generic job/pipeline guidance untouched).
  • skills/databricks-apps/SKILL.md — note the url field from apps get.

python3 scripts/skills.py validate passes (docs-only; no manifest/metadata drift).

This pull request and its description were written by Isaac.

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
@pkosiec pkosiec force-pushed the pkosiec/apps-deploy branch from c850b8b to 83418f0 Compare June 19, 2026 09:04
@pkosiec pkosiec marked this pull request as ready for review June 19, 2026 09:09
@pkosiec pkosiec requested review from a team, lennartkats-db and simonfaltum as code owners June 19, 2026 09:09
@pkosiec pkosiec enabled auto-merge June 19, 2026 10:33
@pkosiec pkosiec added this pull request to the merge queue Jun 19, 2026
Merged via the queue into main with commit da756de Jun 19, 2026
1 check passed
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants