[KV Feedback]: kv write quota exhausted

[jacobheric]

🔍

• [X] Did you search for existing issues?

Type of feedback

Other

Description

I put deno kv into production for a very small blog today and I exhausted my kv writes within like an hour. I don't get much traffic so I'm not 100% sure how this happened.

I'm guessing it was because I put a migration into my main entrypoint file and I was pretty lazy about the migration and updated the data fully every time. I thought this would be ok because it's just two collections of a few hundred records each.

I initially tried to do the migration as part of the deploy build step but nothing got written to the kv there. So it seems loading data in the build step is not possible and loading it in the main entrypoint is excessively redundant.

I'm curious to know if there is a recommended pattern to do migrations of data into production kv. Should I keep it in the main entry point and just wrap it in a dedupe check to make sure it only runs once?

Thanks, Jacob

Steps to reproduce (if applicable)

No response

Expected behavior (if applicable)

No response

Possible solution (if applicable)

No response

Additional context

No response