Skip to content

Implement new endpoints for secrets management #618

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

Open
dmjb opened this issue Jun 3, 2025 · 0 comments
Open

Implement new endpoints for secrets management #618

dmjb opened this issue Jun 3, 2025 · 0 comments

Comments

@dmjb
Copy link
Member

dmjb commented Jun 3, 2025

We need some endpoints for interacting with secrets management.

In future, we may want to allow multiple secrets providers to be set up, but for now, we will restrict ourselves to a single secrets manager. Nonetheless, we will include the name default in some of the endpoints to allow us to change

Proposed endpoints:

POST /secrets/                     # Initialize the default secrets provider
GET   /secrets/default          # Get the details of the default provider - specifically, is it encrypted or 1password
GET   /secrets/default/keys # Get the list of keys from the default provider
POST /secrets/default/keys # Create a new secret (encrypted provider only)
PUT   /secrets/default/keys/{key name}     # Update secret value (encrypted provider only)
DELETE /secrets/default/keys/{key name} # Delete the secret (encrypted provider only)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant