Skip to content

docs: add Genie Code deployment guide - #12

Open
deepbasu123 wants to merge 4 commits into
mainfrom
docs/deploy-with-genie-code
Open

docs: add Genie Code deployment guide#12
deepbasu123 wants to merge 4 commits into
mainfrom
docs/deploy-with-genie-code

Conversation

@deepbasu123

Copy link
Copy Markdown
Collaborator

What

Adds docs/deploy-with-genie-code.md, a deployment guide aimed at Genie Code (the in-workspace assistant). People routinely point Genie Code at this public repo and ask it to deploy the WAF assessment app into their own workspace. Because the app deploys through a Node + Databricks CLI bundle (npm run lifecycle) that cannot run in an ordinary notebook cell, those attempts fail. This guide gives a working in-workspace path, driven from a single notebook via %sh cells:

  • authenticate the CLI from the notebook session (writes a ~/.databrickscfg profile, because the lifecycle wrapper removes the standard Databricks auth env vars)
  • install Node 22 and the Databricks CLI
  • clone and npm ci
  • provision the Lakebase Autoscaling database, pick a SQL warehouse, and write app/.databricks/bundle/customer/variable-overrides.json
  • npm run lifecycle -- validate → preview → --apply
  • verify app state and effective scopes

Why

It sets correct expectations for a common real-world flow and gives it a path that actually completes, while being explicit that this is not the documented supported install path (that remains the laptop / web-terminal route in docs/install.md), with troubleshooting for the shell-path failure modes (egress, cluster access mode, token lifetime, the post-deploy idempotency check).

Verification

Docs-only change; no source or build touched. Commands, the variable-overrides.json path and fields, the npm run lifecycle command lines, the Node/CLI prerequisites, and the app name were checked against docs/install.md, docs/deployment-lifecycle.md, app/databricks.yml, and app/app.yaml. Front-matter and internal links follow the Jekyll house style (title/description/permalink/eyebrow, relative_url).

Deployment impact

None. Adds one published docs page.

This pull request and its description were written by Isaac.

Add docs/deploy-with-genie-code.md, a runbook for deploying the WAF
assessment app from inside a workspace via Genie Code and %sh notebook
cells: authenticate the CLI from the notebook session, install Node 22
and the CLI, clone, provision the Lakebase database and SQL warehouse
binding, write variable-overrides.json, run npm run lifecycle, verify.

States plainly that this is not the documented supported install path
(that stays the laptop / web-terminal route in install.md) and links to
it, with troubleshooting for the shell-path failure modes.

Co-authored-by: Isaac <no-reply@databricks.com>
deepbasu123 and others added 3 commits August 31, 2026 07:37
Add a short callout under Get started pointing to the Deploy with Genie
Code guide as an in-workspace alternative to the supported Asset Bundle
path.

Co-authored-by: Isaac <no-reply@databricks.com>
Rework docs/deploy-with-genie-code.md so it states the deployment
objective and the app-specific facts Genie Code cannot infer (the four
bindings, the lifecycle command, the auth/scope constraints) and lets
Genie Code work out the mechanics, instead of prescribing a fixed %sh
script.

Replace the terminal-only verify step with a Python SDK self-check that
authenticates as the notebook user (no profile needed), tests app state,
deployment status, on-behalf-of scopes and resource bindings, prints a
PASS/FAIL per check and an overall verdict, and adds a rubric for
reading it. Honest "not the supported path" framing preserved.

Co-authored-by: Isaac <no-reply@databricks.com>
Remove the "what you can and cannot do" section and the cannot-infer /
cannot-guess / %sh-availability phrasing. Keep the app-specific facts,
prerequisites, deploy command, and the self-check; move the one "not the
supported path" note to the intro.

Co-authored-by: Isaac <no-reply@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.

1 participant