Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI command to list available providers #110

Open
tegefaulkes opened this issue Jan 30, 2024 · 1 comment
Open

CLI command to list available providers #110

tegefaulkes opened this issue Jan 30, 2024 · 1 comment
Labels
development Standard development r&d:polykey:core activity 3 Peer to Peer Federated Hierarchy

Comments

@tegefaulkes
Copy link
Contributor

Specification

Right now we only have github as a provider. But there is no way to know what providers are available unless you look at the source code.

To this end we need to add a polykey identities providers command (name pending) that will list all supported providers.

Functionality may need to be added to Polykey to support this.

We can also look into adding a list of providers to the help text of the command?

Additional context

Related: #40

Tasks

  1. Add a CLI command to list supported providers.
@tegefaulkes tegefaulkes added the development Standard development label Jan 30, 2024
@CMCDragonkai
Copy link
Member

Because provider integration will later be dynamic with plugin support (MatrixAI/Polykey#166 and https://github.com/MatrixAI/Polykey/issues?q=is%3Aissue+is%3Aopen+providers), it does need to be an actual command itself.

So yes pk identities providers is a useful way of listing all providers, including which ones are natively integrated and which ones are plugins.

Plugins are likely be wasm integrated - this makes it easy for us to call code in a safe way (sandboxing) and allow contributors to write in whatever language they please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Standard development r&d:polykey:core activity 3 Peer to Peer Federated Hierarchy
Development

No branches or pull requests

2 participants