feat(console): Studio datasource manager — test & sync objects from a datasource#1839
Merged
Merged
Conversation
… datasource
Adds a System → Datasources surface that wraps the framework datasource-admin
REST routes (a control-plane concern that lives outside the generic
metadata-admin engine):
- List runtime datasources (GET /api/v1/datasources) with driver/status/origin.
- Test connection (POST /api/v1/datasources/:name/test) → toast with latency.
- Sync objects: introspect remote tables (GET …/remote-tables), pick which to
import, generate an object definition per table (POST …/object-draft), and
create each through the normal metadata channel (MetadataClient.save('object', …)).
Wires the route under system/datasources and adds a System hub card for
discoverability. Verified end-to-end against a live sqlite datasource: test
returns ok, and syncing customers/orders creates real object metadata with the
introspected fields.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
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.
What
Adds a System → Datasources surface to the console so admins can manage runtime datasources and sync external tables in as objects — the long-missing "test datasource + sync objects" flow, now wired into the Studio design experience.
This is a control-plane concern (datasource lifecycle) that intentionally lives outside the generic metadata-admin engine, wrapping the framework
datasource-adminREST routes.Features
GET /api/v1/datasources) — driver, status, origin.POST /api/v1/datasources/:name/test) → toast with latency.GET …/remote-tables) → pick tables → generate an object definition per table (POST …/object-draft) → create each via the normal metadata channel (MetadataClient.save('object', …)).system/datasources.Depends on
Framework #2085 (read-only introspection routes + by-name test). Merge that first.
Verification (live, browser)
Against a live sqlite datasource (
demo_ext):demo_extdemo_ext: connection ok (1ms)customers/orders→ select both → Create 2 objects → both created as real object metadata (object count 79 → 81;customershas fieldsid, name, email, created_at, bound todemo_ext)🤖 Generated with Claude Code