denoland / denoland/deploy_feedback

[KV Feedback]:

Open
#727 0 comments 0 reactions 0 assignees View on GitHub
kv
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

### 🔍

- [ ] Did you search for existing issues?

### Type of feedback

Feature request

### Description

I need the ability to upload a json document in the expected KV format of [keys,...]: row , otherwise populating a large store from the client side will take weeks. The workaround: to deploy and include a source document in json format is inconvenient at the moment, since I am migrating away from another vendor's noSQL solution and is not in a complete state. Otherwise an ability to batch-set documents would be really helpful.

### Steps to reproduce (if applicable)

1. dump noSQL to JSON document
2. write deno script to populate live KV store
3. Wait

### Expected behavior (if applicable)

_No response_

### Possible solution (if applicable)

A web console based feature that will accept a (zipped?) JSON document and validate that the structure of the document is acceptable, then if so create/replace an existing KV store.

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start by reviewing the Deno Deploy KV console and existing KV population options, then clarify the accepted JSON structure and validation behavior. Done means a large KV store can be populated from a validated JSON document or through batch setting without the described client-side wait.

Written by the indexing model from the issue text.

Assessment

Tech stack
deno
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.