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

Use the secrets manager #53

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

brichet
Copy link
Collaborator

@brichet brichet commented Mar 6, 2025

This PR uses the secrets manager to handle passwords in settings.

The tests are not intended to work, since the secrets manager package has not been published yet.
To test it, one should install locally jupyter-secrets-manager and use yalc to link the Javascript package.

@brichet brichet added the enhancement New feature or request label Mar 6, 2025
@brichet brichet marked this pull request as ready for review March 11, 2025 15:45
@@ -137,19 +138,20 @@ const providerRegistryPlugin: JupyterFrontEndPlugin<IAIProviderRegistry> = {
id: '@jupyterlite/ai:provider-registry',
autoStart: true,
requires: [IFormRendererRegistry, ISettingRegistry],
optional: [IRenderMimeRegistry],
optional: [IRenderMimeRegistry, ISecretsManager],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like with this change, API keys are not stored on the page anymore since it will be using the default in-memory secret manager?

Wondering if we should still have a secret manager that stores secrets in the browser, for convenience? Or maybe have an option to choose between in-memory and in-browser storage?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants