[KV] Added KV bindings documentation for preview_id

[thomasgauvin]

Addresses https://discord.com/channels/595317990191398933/874727019479437372/1269012391937445910

[cloudflare-workers-and-pages[bot]]

Deploying cloudflare-docs with    Cloudflare Pages

Latest commit:	c7bffeb
Status:	✅  Deploy successful!
Preview URL:	https://bcf0f95c.cloudflare-docs-7ou.pages.dev
Branch Preview URL:	https://thomasgauvin-update-kv-bindi.cloudflare-docs-7ou.pages.dev

View logs

[github-actions[bot]]

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/kv/concepts/kv-bindings/	https://thomasgauvin-update-kv-bindi.cloudflare-docs-7ou.pages.dev/kv/concepts/kv-bindings/
https://developers.cloudflare.com/kv/get-started/	https://thomasgauvin-update-kv-bindi.cloudflare-docs-7ou.pages.dev/kv/get-started/

[thomasgauvin]

Resolved merge conflicts

[jldec]

small suggestion:

How about adding a note about the --preview and --local flags for wrangler kv cli commands?

I found it a bit surprising that touching a kv namespace from worker code withwranger dev writes to the local (dev) version of the namespace, but that wrangler kv cli commands appear to require both --local and --preview to see those changes.

The screenshot below shows wrangler commands after writing 2 different kv values with wrangler dev and just one with wrangler dev --remote

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11021221	Triggered	Generic High Entropy Secret	baadb77cce32bf338806c90b8af6f37d5356c9db	astro.config.mjs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}