Warn in ucode setup when an MPS isn't usable by all workspace users - #303
Merged
Conversation
An admin can pick a Model Provider Service whose schema isn't granted to the workspace, and developers who later pull that managed config hit "User does not have USE_SCHEMA on Schema <catalog>.<schema>" at launch. After the admin selects an MPS, check whether the `account users` group has USE_SCHEMA on its schema (via UC effective-permissions, so a catalog-level grant counts) and print a non-blocking warning if not. It only warns: access may instead come from a team group the check can't see, and an inconclusive check (API unreachable) stays silent rather than crying wolf. Also isolate ENABLE_MANAGED_AGENT_CONFIG in the test fixture so the dev's shell env can't change CLI behavior mid-test. Co-authored-by: Isaac
tt-le
self-requested a review
August 10, 2026 15:41
tt-le
approved these changes
Aug 10, 2026
AarushiShah-db
enabled auto-merge (squash)
August 10, 2026 16:04
AarushiShah-db
disabled auto-merge
August 10, 2026 16:07
AarushiShah-db
enabled auto-merge (squash)
August 10, 2026 16:07
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.
An admin can pick a Model Provider Service whose schema isn't granted to the workspace, and developers who later pull that managed config hit "User does not have USE_SCHEMA on Schema ." at launch. After the admin selects an MPS, check whether the
account usersgroup has USE_SCHEMA on its schema (via UC effective-permissions, so a catalog-level grant counts) and print a non-blocking warning if not.It only warns: access may instead come from a team group the check can't see, and an inconclusive check (API unreachable) stays silent rather than crying wolf.
Also isolate ENABLE_MANAGED_AGENT_CONFIG in the test fixture so the dev's shell env can't change CLI behavior mid-test.
Co-authored-by: Isaac