Skip to content

[KV] add note on bulk reads for pricing #22207

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

Merged

Conversation

thomasgauvin
Copy link
Contributor

No description provided.

Copy link
Contributor

hyperlint-ai bot commented May 5, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Updated Workers KV pricing documentation to clarify bulk read operations.

  • Modified the pricing table to specify keys read, written, and deleted.
  • Added a note explaining that bulk read operations are billed per key read.

Modified Files

  • src/content/partials/workers/kv_pricing.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

Copy link
Contributor

github-actions bot commented May 5, 2025

@thomasgauvin thomasgauvin merged commit fbb5bb6 into production May 6, 2025
13 checks passed
@thomasgauvin thomasgauvin deleted the thomasgauvin-adjust-kv-pricing-bulk-requests branch May 6, 2025 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants