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.

Sign up for GitHub

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

Jump to bottom

Secrets Manager #7

Open

FossPrime opened this issue Jun 8, 2023 · 0 comments

Labels

Collaborator

FossPrime commented Jun 8, 2023 •

edited

Loading

This is a proposal how to get secrets working

In localStorage keep a JSON document with the following:

- '^github.com/kat-tax/.*':
  - OPENAI_KEY: '...'
  - TWILIO_KEY: '...'
- '^gitlab.com/':
  - SERVICE_ACCOUNT: '…'
- 'nsa.com/area-51-crm.git'
  - $match: 'exatct'
  - ALIEN_OS_KEY: '...'

Allow users to edit it via a vslite.secrets.yaml virtual file in the root directory. The file could actually be in /tmp/.
Automatically load it from localStorage on boot.

default to exact match for performance. Web containers have zero access to master local storage by default... So this is safe ceteris paribus.

Settings Sync could be accomplished with a browser extension (100KB):

Things left to consider

There should be a way for git to request a token and have the user grant access per cloned repo... as any cloned repo could commandeer the token.

The text was updated successfully, but these errors were encountered:

TheUltDev changed the title ~~[FR] Local secrets manager~~ Local secrets manager

TheUltDev added the enhancement label

TheUltDev changed the title ~~Local secrets manager~~ Secrets manager

TheUltDev changed the title ~~Secrets manager~~ Secrets Manager

FossPrime mentioned this issue

Secrets API #32

Draft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment