Repository navigation
Add Privy CLI - #11
Open
awesamarth wants to merge 1 commit into
Open
awesamarth wants to merge 1 commit into
awesamarth wants to merge 1 commit into
Conversation
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.
Adds Privy CLI to Infrastructure And Cloud, next to Firebase CLI.
Disclosure: I'm the author. It's unofficial and not affiliated with Privy; the README, docs and npm description say so.
Privy has no first-party CLI for managing accounts and apps, so this covers what you would otherwise click through in the dashboard: creating apps, login methods and OAuth providers, users, wallets, policies, webhooks, team members and analytics. It talks to the dashboard's HTTPS endpoints directly; it does not drive a browser.
Evidence:
privy schema <command>andprivy cli searchfor discovery: agents guide--yesis passed; production changes additionally need--allow-production: app lifecycleauth loginrenews a saved session without a TTY. It is a full dashboard session, not a scoped token: authentication--dry-runvalidates offline,--diffcompares against the live app before writing, and writes are read back afterwards: example{"error": {"code", "message", "status", "hint", "requestId"}}on stderr, with exit code 2 for usage errors and 130 for cancellation: src/cli.tsCaveat, also in the entry: most of the endpoints it uses are undocumented dashboard APIs, so a dashboard change can break a command until the CLI is updated. It does not sign wallet transactions or export private keys.