Skip to content

feat(ui): providers page with a published providers document - #1452

Merged
kvlonge merged 3 commits into
mainfrom
feat/ui-providers
Nov 13, 2026
Merged

kvlonge merged 3 commits into
mainfrom
feat/ui-providers

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Why

The Providers page only had mock data. A server had no record of a project's providers, so people could not see which settings a deployment needs or which jobs depend on a provider.

Changes

  • Location publishing adds a providers snapshot document when a project declares providers: name, class, docstring, file, each setting's name, type, required flag, secret flag and environment variable, and the code that takes the provider (loaders, tasks, hooks, materializations and so on). Setting values and defaults are never read or published.
  • New person read GET /api/control/locations/{location_id}/targets/{target}/providers, gated like the other listings (view on every node of the publication). Each provider also lists the jobs whose selection runs its code.
  • The UI Providers list shows the class and usage summary. A provider page has a Settings tab (type, environment variable, required, secret marker) and a Used by tab (code and the jobs that run it).
  • Environment variable names follow pydantic-settings: an AliasChoices or AliasPath alias names the variable, and env_prefix_target decides whether the prefix applies to aliases, field names or both.
  • TypeScript client regenerated; docs and the packaged docs skill updated on the providers and server pages.

DuckShop edge cases: this is a new read, not a fix for a project shape, data value or lifecycle sequence, so no edge case is added.

Verification

  • Orchestration contract test for the providers read on SQLite and PostgreSQL, including job matching and the listing permission.
  • Integration tests publish projects with secrets, defaults, AliasChoices and env_prefix_target='alias', and assert the document carries the metadata and none of the values.
  • UI: svelte-check, vitest (new mapping test), and rendered screenshots of the list, Settings and Used by tabs against sqb dev and mock data.
  • make check-ci on the final head.

@kvlonge kvlonge added the full-verify Run the full Verify matrix on this pull request label Nov 13, 2026
@kvlonge
kvlonge enabled auto-merge November 13, 2026 17:33
The CLI imports project_modules at startup, so a module-level pydantic
import broke the startup import footprint.
# Conflicts:
#	crates/sqlbuild-python/src/bindings/_helpers/location_command/constants.rs
@kvlonge
kvlonge added this pull request to the merge queue Nov 13, 2026
Merged via the queue into main with commit b0500b0 Nov 13, 2026
53 checks passed
@kvlonge
kvlonge deleted the feat/ui-providers branch November 13, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-verify Run the full Verify matrix on this pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant