Conversation
Plumb DOCINTEL_WAREHOUSE_ID through bundle as --var warehouse_id in bootstrap + CI so dashboard/serving env match wait_for_kpis and log_and_register, instead of falling back to the lookup-by-name default that fails in workspaces lacking "Serverless Starter Warehouse". Add an explicit `bundle run index_refresh` after stage-2 first-deploy because the table_update trigger doesn't fire retroactively on rows already produced by the stage-2 pipeline run. README fixes: include pytest in install line, add DOCINTEL_WAREHOUSE_ID + .venv/bin/python to the steady-state agent registration command, and correct the env-var-table description (the var isn't read by the eval). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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
1 participant
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.
Summary
DOCINTEL_WAREHOUSE_IDthrough the bundle as--var warehouse_idinscripts/bootstrap-dev.shand.github/workflows/deploy.yml, so the dashboard + serving env match whatwait_for_kpis/agent/log_and_register.pyuse. Without this, the bundle falls back to itslookup: warehouse: Serverless Starter Warehousedefault — which fails validation in workspaces lacking that named warehouse and silently picks a different ID otherwise.databricks bundle run … index_refreshafter stage-2 first-deploy inbootstrap-dev.sh. Thetable_updatetrigger does not fire retroactively on rows already produced by the stage-2 pipeline run, so the VS index never materialized on a fresh workspace until the next pipeline run.sync_index.pyis create-if-missing/sync-if-exists, so this stays idempotent.pytestin the install line so the documentedpytest agent/tests/works after install; addDOCINTEL_WAREHOUSE_IDand.venv/bin/pythonto the steady-state agent registration command (the script reads the var; macOS doesn't shippython); correct the env-var table description forDOCINTEL_WAREHOUSE_ID— it isn't read byevals/clears_eval.py.Test plan
bash -n scripts/bootstrap-dev.shdatabricks bundle validate --strict -t dev→Validation OK!databricks bundle validate --strict -t prod→ fails as designed withoutservice_principal_id.venv/bin/python -m pytest agent/tests/ -q→ 18 passed./scripts/bootstrap-dev.sh(requires real workspace; not run locally — review the diff against the runbook before merging)vars.DOCINTEL_WAREHOUSE_IDis set in the repo (the validate step now reads it)🤖 Generated with Claude Code