Agent Templates: use uv.lock#201
Merged
bbqiu merged 3 commits intodatabricks:mainfrom Apr 29, 2026
Merged
Conversation
bbqiu
changed the title
Co-authored-by: Isaac Signed-off-by: Bryan Qiu <bryan.qiu@databricks.com>
Replace internal Databricks PyPI proxy URLs with public pypi.org so external customers can install dependencies from these templates. Co-authored-by: Isaac Signed-off-by: Bryan Qiu <bryan.qiu@databricks.com>
bbqiu
changed the title
fanzeyi
approved these changes
Apr 28, 2026
3 tasks
dhruv0811
added a commit
that referenced
this pull request
Apr 30, 2026
The previous scrub of UV_EXCLUDE_NEWER alone wasn't sufficient.
CI run 25147991251 deploy logs show two distinct contamination
messages, not one:
[BUILD] Ignoring existing lockfile due to removal of global exclude newer
[BUILD] Ignoring existing lockfile due to removal of exclude newer
for package `databricks-openai`
The first is UV_EXCLUDE_NEWER (already scrubbed). The second comes
from the runner repo's `uv.toml` `[exclude-newer-package]` overrides
for databricks-openai / databricks-ai-bridge / databricks-langchain /
databricks-agents. uv discovers that config file by walking up from
the template subdir to the workspace root — so popping UV_CONFIG_FILE
alone doesn't help.
Fix: pop UV_CONFIG_FILE *and* set UV_NO_CONFIG=1 to disable walk-up
discovery entirely. Now both contamination sources are blocked at the
process level for any subprocess helpers.py spawns, and the
template's checked-in lockfile reaches the Apps runtime byte-identical
to what Bryan committed in #201.
Co-authored-by: Isaac
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
2 participants
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.
with support for
uvas a package manager and the whitelisting of our databricks-ai-bridge packages, set uv.lock so all dependencies are downloaded before the deployment is marked as readyhttps://docs.databricks.com/aws/en/dev-tools/databricks-apps/dependencies#define-python-dependencies-with-uv
verified these apps work by running integration tests + deploying to prod app without access to internal registry