feat(onepassword): support service account datasource#280
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
onequery-landing | 935314b | Commit Preview URL Branch Preview URL |
Jun 12 2026, 08:37 AM |
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
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.
One-Line Summary
1Password data sources can now connect with Service Account tokens for read-only vault, item, and secret-reference access.
User-Facing Changes
authMethod: "service_account"withserviceAccountTokeninstead of requiring a Connect Server URL.list_vaults,list_items,get_item, andresolve_secretsource API operations.authMethod: "connect",apiBaseUrl, andaccessToken.Why This Changed
The previous 1Password provider only modeled the self-hosted Connect Server REST API. 1Password Service Accounts authenticate through the official SDK/CLI flow rather than a Connect-style cloud
apiBaseUrl, so users could not add the cloud Service Account datasource without standing up Connect Server.How It Changed
Extra Context / Decisions
fetch_apirequests, request bodies, and custom headers so the token only enables the supported read-only operations.Verification
bun run typecheckinpackages/serverbun run test src/source-api/adapters/simple-rest-providers.test.tsinpackages/serverbun run test src/credentials.test.tsinpackages/dbbunx turbo typecheck --filter=@onequery/server --filter=@onequery/db --filter=@velen/web --filter=@velen/db --jsonfrom Velen rootbunx turbo test --filter=@onequery/server --filter=@onequery/db --filter=@velen/web --filter=@velen/db --jsonfrom Velen rootVideo / Screenshot (Optional)