You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.
If users add kv-namespaces snippet under a [site] config, the namespace is not parsed into a Wrangler Manifest so the namespace is still inaccessible to a worker.
I think option 1 is by far the best option. Option 2 doesn't play well with folks who have different environments and don't necessarily want to put their kv-namespaces up in the top-level config.
instead? This way, there is no way kv-namespaces will be accidentally lumped under sites. We can also stop users from getting confused between sites and environments...
cc @steveklabnik
If users add
kv-namespaces
snippet under a[site]
config, the namespace is not parsed into a WranglerManifest
so the namespace is still inaccessible to a worker.We should do two things here:
Alternatively we could just rewrite their toml for them but that gets a little hairy, especially if they have things like comments
The text was updated successfully, but these errors were encountered: