-
Notifications
You must be signed in to change notification settings - Fork 140
Add KV inspector with backend endpoints and frontend UI #3627
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
Co-authored-by: jog1t <39823706+jog1t@users.noreply.github.com>
Co-authored-by: jog1t <39823706+jog1t@users.noreply.github.com>
|
@copilot please add ui for this feature in frontend repository, similarly to how actor events, and state is presented |
Co-authored-by: jog1t <39823706+jog1t@users.noreply.github.com>
I've added the KV inspector UI to the frontend, following the same patterns as actor events and state tabs. The implementation includes: UI Components:
Features:
Integration:
The UI is ready and will display KV entries once the backend driver implementation is complete (the Changes committed in dc6fcc5 |
Implements complete KV inspector feature to view and search actor key-value storage across datacenters.
Changes
Backend API Endpoints
GET /actors/{actor_id}/kv/keysto api-public and api-peer with query parameters:prefix: Base64-encoded key prefix filterlimit: Result count (default 100, max 1000)reverse: Sort orderInspector Protocol
getKvEntries()accessor method/kvroute to inspector router with query parameter supportActorFeature.Kvenum value for feature detectionFrontend UI
actor-kv-tab.tsx- Tab wrapper with loading/error statesactor-kv.tsx- Main view with search functionality and grid layoutactor-kv-list.tsx- Entry renderer with base64 decoding and JSON parsingUI Features:
Remaining Work
To complete the feature:
getKvEntries()accessor in FileSystemActorDriver and EngineActorDriver using existingkvListPrefixmethodsThe backend and frontend follow existing patterns from the
kv_getendpoint and Events/State tabs, with consistent base64 encoding for keys/values.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.