Repository navigation
[ML-70358] [s] Name added user API scopes and the tools requiring them during deploy - #739
Draft
junchoi-db wants to merge 3 commits into
Draft
junchoi-db wants to merge 3 commits into
junchoi-db wants to merge 3 commits into
Conversation
jamesbxwu
changed the title
jamesbxwu
changed the title
2 of 4 tasks
This branch has not been deployed
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
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.
Adding a user-auth web-search tool implicitly requires
ai-gateway, but the bug bash saw only a generic scope-change warning. Deploy now names added scopes and the tool or explicit manifest entry requiring each one. The same explanation appears when preflight stops an existing App before--allow-user-scope-updateis granted. Redeploys with existing scopes report them as unchanged and avoid a re-consent warning.Scope inference remains shared with the existing planner, including UC functions, Genie, and sandbox policy scopes. The CLI reference distinguishes API scopes from Unity Catalog data privileges. This change does not grant additional permissions or alter scope-update consent.
Design doc: n/a (customer journey feedback).
Proof of work
82 targeted deploy/auth tests passed. New regression cases cover the previously missed existing-App permission error for web search, UC functions, sandbox volume access, and explicit
[auth.user].additional_api_scopes. They verify the missing scope and binding are named before any App create/update call.For example, a user-auth sandbox volume binding reports
filesand itssystem.ai.sandboxbinding, while preserving an unrelated existingsqlscope. Read-only managed-tool discovery also completed successfully.Live deployment and unchanged-scope redeployment remain blocked before mutation by the execution environment's approval gate. They are not claimed as completed E2E.
A controlled local existing-App SDK stub also exercised the actual preflight path: it named
ai-gateway,files,mcp.functions, andworkspace.workspacewith the requiring bindings, and recorded zero App create/update calls. This is a local contract check, not a live deployment.Tested commit:
aa558cd922e9c0ba3fa4fd7b367c3427391f471f.Validation
82 tests passed; JUnit verified. Ruff formatting/lint and targeted type checks passed. Tests cover added and unchanged scopes, user versus App bindings, and explicit manifest sources.
CI remains blocked by six pre-existing ordering assertions in
template_langgraph_history_test.py:240. The same assertions fail on base commita8d55f4074f4d58b979f8fe9cd22058936eba779: https://github.com/databricks/databricks-ai-bridge/actions/runs/38662891535. This PR remains a draft.This pull request and its description were written by Isaac.