Repository navigation
Add Xata and SingleStore providers - #303
Merged
Merged
Conversation
Both sign in with a pasted key for now. Xata: an API key lists every branch of every project and connects with the branch's own credentials. SingleStore: a Management API key lists workspaces and starter workspaces; the API never returns a database password, so it is asked once and kept, as with Supabase. Both can move to OAuth later: Xata supports dynamic client registration, SingleStore needs a client ID.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
…/branches/{id}/credentials), TLS on.*.xata.techand*.svc.singlestore.comare recognised as these providers; SingleStore gets its brand mark, Xata a drawn X.Both move to OAuth later: Xata's Keycloak allows dynamic client registration (verified), SingleStore needs a client ID from them. LiteFS isn't a hosted service and isn't added.
Unit tests cover the credential mapping; a bad key returns 401 on every endpoint used (checked against the live APIs), which puts the key form back. Not yet run against real accounts.