deploy

name: deploy description: Use when the user asks to deploy, ship, release, or push OntoBricks to Databricks. Wraps the Databricks Asset Bundle deploy for the FastAPI app and the MCP server, with the bootstrap-perms safety net described in README.md.

Deploy OntoBricks

The canonical deploy steps are in README.md §Deploying / Installing and .cursorrules §"When asking to deploy". The Make targets live in Makefile. This skill only sequences pre-flight and post-deploy checks.

Pre-flight (verify before invoking make)

1. databricks --version — CLI present.
2. databricks auth describe — authenticated against the right workspace. If not, use the databricks-authentication skill.
3. git status — clean tree (or user has acknowledged uncommitted changes).
4. uv run pytest -q — tests pass. Do not deploy on red.

Deploy

make deploy runs scripts/bootstrap-app-permissions.sh automatically on the first deploy (see README.md). If the user runs databricks bundle deploy directly, run make bootstrap-perms once afterwards (idempotent).

Post-deploy

1. Compute > Apps > ontobricks > Resources — confirm sql-warehouse and volume are bound. If missing, the user must bind them manually (binding cannot be done via DAB).
2. Logs — confirm startup completed cleanly.
3. If the registry volume is empty, tell the user to open Settings > Registry > Initialize in the app UI.
4. Hit /healthz to confirm the FastAPI app is responsive.

Release flow

When the user says "release vX.Y.Z" rather than just "deploy":

1. make test
2. Bump version in pyproject.toml
3. git add -A && git commit -m "Release vX.Y.Z" && git tag vX.Y.Z && git push origin main --tags
4. make deploy (or make deploy-prod)
5. Update the changelog (changelog skill).

Don't

• Don't deploy without running tests.
• Don't databricks bundle deploy directly without remembering make bootstrap-perms for first-time deploys.
• Don't claim deploy is done until the app status is confirmed (or the user accepts deploy-no-run).