You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Changes
* Added AppKit template
* Removed tRPC template
* Introduced go templates for interpolating files from the template
* Removed `--allow-deployment` configuration. It's defaulting to `true`
now.
* The new template features
* AppKit support (bundled dependency)
* Playwright for E2E smoke test validation
* DABs pre-configured (not currently used but will be in the future)
## Why
<!-- Why are these changes needed? Provide the context that the reviewer
might be missing.
For example, were there any decisions behind the change that are not
reflected in the code itself? -->
## Tests
Creating dozens of NYC taxi apps
<!-- If your PR needs to be included in the release notes for next
release,
add a separate entry in NEXT_CHANGELOG.md as part of your PR. -->
---------
Co-authored-by: Pieter Noordhuis <pieter.noordhuis@databricks.com>
Your session in Databricks MCP has been successfully initialized. Here are the guidelines to follow while working on projects using databricks_mcp tools:
2
2
3
3
## Project State Management:
4
-
This project uses a state file (`.edda_state`) managed by edda MCP to enforce the correct workflow order:
5
-
1. **Scaffolded**: `scaffold_data_app` creates project structure from template (starts in this state)
6
-
2. **Validated**: `validate_data_app` runs build + tests, computes BLAKE3 checksum of package.jsonand all core source files
4
+
This project uses a state file (`.edda_state`) managed by Databricks MCP to enforce the correct workflow order:
5
+
1. **Scaffolded**: `scaffold_databricks_app` creates project structure from template (starts in this state)
6
+
2. **Validated**: `validate_databricks_app` runs build + tests, computes a checksum of package.jsonand all core source files
7
7
3. **Deployed**: `deploy_databricks_app` deploys to Databricks Apps, but ONLY if checksum hasn't changed since validation
8
8
9
9
Re-validation is allowed (Deployed → Validated) to update the checksum after intentional changes. The databricks_mcp tools enforce these state transitions and prevent invalid state changes.
@@ -15,4 +15,4 @@ Re-validation is allowed (Deployed → Validated) to update the checksum after i
15
15
- When working with Databricks or other services, use real API calls in tests (no mocks) to verify end-to-end functionality, unless explicitly instructed otherwise. It can be done on subset of data if applicable.
16
16
- Do NOT create summary files, reports, or README unless explicitly requested
17
17
- When not sure about the user's intent, ask clarifying questions before proceeding. For example, if user asks for "a data app to analyze sales data", ask for more details on data sources and analysis goals. Do not make assumptions regarding their needs and data sources.
18
-
- However, stick to the technical stack initialized by the `scaffold_data_app` as it has been approved by the management and battle-tested in production.
18
+
- However, stick to the technical stack initialized by the `scaffold_databricks_app` as it has been approved by the management and battle-tested in production.
"It is recomended to run the app in the background immediately after scaffolding using `npm install && npm run dev`. Then directly open http://localhost:8000 in the browser so the user can follow the progress.\n\n"+
15
+
"IMPORTANT: Make sure to read %s before proceeding with the project!!!\n\n",
0 commit comments