Skip to content

feat: Role aware ucode configure for mcp, skills, spend-tiers subcommands - #418

Open
tt-le wants to merge 3 commits into
mainfrom
tien/configure-managed-sections
Open

feat: Role aware ucode configure for mcp, skills, spend-tiers subcommands #418
tt-le wants to merge 3 commits into
mainfrom
tien/configure-managed-sections

Conversation

@tt-le

@tt-le tt-le commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

Added role aware subcommands:

ucode configure spend-tiers
ucode configure mcps
ucode configure skills

Workspace admin

Screenshot 2026-08-30 at 10 04 15 PM Screenshot 2026-08-30 at 10 04 49 PM Screenshot 2026-08-30 at 10 05 15 PM

Non workspace admin

Blocking admin only command:
Screenshot 2026-08-30 at 10 08 54 PM
ucode configure mcps, skills are still routing to the dev version when the user is not an admin.
Screenshot 2026-08-30 at 10 10 33 PM

tt-le and others added 3 commits August 31, 2026 00:36
Move the managed-config section authoring from `ucode setup <section>` onto
the role-aware `ucode configure`, so it survives the `ucode setup` removal
(AIGTWY-4342) and matches the ug IA (admin authoring stays in the CLI only
temporarily, until the Databricks UI/REST/TF surfaces land).

- `ucode configure spend-tiers`: new admin-only command wrapping
  setup_budget_policy_command (no developer form, so it always authors).
- `ucode configure mcp` / `ucode configure skills`: now role-aware, mirroring
  bare `ucode configure`. A workspace admin (with ENABLE_MANAGED_AGENT_CONFIG
  set) authors the managed config's MCP servers / skills; a developer
  configures their own tools. Gated by the flag, so with it off these stay
  developer-only exactly as before. Admins wanting personal MCP servers use
  `ucode mcp add`/`remove`.
- Repoint the authoring flow's "Next steps" list at the `ucode configure`
  section commands.

`ucode setup <section>` still works; its removal is the separate AIGTWY-4342
deprecation.

Co-authored-by: Isaac <no-reply@databricks.com>
…strings

The old name described how the result is used, not what the function checks;
it's a predicate for "is the caller a workspace admin (with the feature on)".
Also tighten its docstring and configure_spend_tiers' to state behavior
rather than caller context.

Co-authored-by: Isaac <no-reply@databricks.com>
`ucode configure mcp`/`skills` authenticate once in `_is_managed_config_admin`
to pick the admin-vs-developer branch, then the chosen branch authenticates
again — printing "Databricks auth already available" twice. Pass quiet=True to
the pre-check's ensure_databricks_auth (as setup_command already does) so only
the branch reports it. A real login is never silenced by quiet.

Co-authored-by: Isaac <no-reply@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant