Refactor: api key creation/retrieval/deletion to use infra api #68
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ben-fornefeld
force-pushed
the
use-crud-endpoints-for-api-keys-access-tokens-in-dashboard-e2b-1588
branch
from
cd273a5 to
695efb3
Compare
dobrac
reviewed
May 23, 2025
Co-authored-by: Jakub Dobry <jakub.dobry8@gmail.com>
dobrac
approved these changes
May 26, 2025
ben-fornefeld
deleted the
use-crud-endpoints-for-api-keys-access-tokens-in-dashboard-e2b-1588
branch
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.
To support secret hashing, the dashboard should rely on the infra api to handle api-keys. This pr refactors the key management to use the dedicated infra apis instead of direct db access.
Also completes E2B-2352