Uh oh!
There was an error while loading. Please reload this page.
fix: align provisioning-adapter service key; clarify turso lives in cloud repo - #1395
Merged
Conversation
Fix the leftover from the project→environment rename: the provisioning- adapter registry is now read under the canonical 'environment-provisioning-adapters' key (matching the cloud tenant plugin and this file's own in-code comment), falling back to the legacy 'project-provisioning-adapters' key for older hosts not yet rebuilt. Affects listRegisteredDrivers() and getRealAdapter() in handleCloud(). Runtime suite: 314 passed.
…ramework Framework bundles only memory/sql/sqlite-wasm/mongodb drivers. The libsql/turso driver was extracted to @objectstack/driver-turso in the cloud repo (May 2026) and is loaded via dynamic import on demand. Correct three stale docs that implied framework ships a turso driver, so agents don't add libsql code to framework or assume the unified SQL driver speaks libsql: - README feature list + metrics table - http-dispatcher listRegisteredDrivers comment (unified sql backends are better-sqlite3/pg/mysql2 only) Comment/doc-only; no behavior change.
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…atcher Delete handleCloud + deleteProjectCascade from HttpDispatcher and the 26 /cloud/* route registrations from dispatcher-plugin. These are cloud control-plane concerns (environment provisioning, org cascade delete, membership, per-environment package installs) that have been relocated to the cloud repo's @objectstack/service-cloud (routes/environment-crud.ts), with byte-identical /cloud/* paths and response envelopes so the @objectstack/client `projects` namespace is unaffected. Also drop the orphaned resolveCallerUserId helper, its now-unused import, and the /cloud dispatch branch. The resolveEnvironmentContext /cloud skip-guards are kept — control-plane paths must never be treated as env-scoped.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Summary
Two generic, turso-agnostic framework changes split out of the cloud-side
"remove built-in templates / turso-only" work. All turso policy stays in
the cloud repo — framework stays neutral.
1.
http-dispatcher.ts— service-key alignment (bug fix)The provisioning-adapter registry was renamed
project-provisioning-adapters→
environment-provisioning-adapters(project→environment rename), but theframework dispatcher still read the old key. This left
listRegisteredDrivers()and
getRealAdapter()unable to see adapters registered by the cloud tenantplugin / objectos host, surfacing as
Unknown driver 'turso'. Available: [memory].Fix reads the canonical
environment-provisioning-adapterskey first and keepsproject-provisioning-adaptersas a fallback for older hosts not yet rebuilt.2. Docs cleanup — turso is NOT bundled in framework
The libsql/turso driver was extracted to
@objectstack/driver-tursoin thecloud repo (May 2026) and is loaded via dynamic import on demand. Corrected
three stale docs that implied framework ships a turso driver, so agents don't
add libsql code to framework or assume the unified SQL driver speaks libsql:
http-dispatcherlistRegisteredDriverscomment (unified sql knex backendsare better-sqlite3 / pg / mysql2 only)
Risk
Low. Change 1 is a one-line key lookup with a backward-compatible fallback;
change 2 is comment/doc-only. No behavior change beyond restoring adapter
discovery. No publish / version bump.
Test