wrangler ignores KV bindings in config

TomatoCake · 2023-07-25T06:15:56.880Z

I've used the following in my wrangler.toml: ```toml kv_namespaces = [ { binding = "BROWSER_SCREENSHOT_CACHE", id = "xxx" } ] ```. However, once I deploy the worker, the KV binding gets removed and is no longer available in the code and not visible in the dashboard as binded. However, I can add it in the dashboard and it works (Using the wrangler.toml code by the dash doesn't change anything, it's the same)

T

Tin Cap•7/25/23, 4:34 PM

Any chance you have different configuration parameters for different environments?

T

TomatoCakeOP•7/25/23, 4:59 PM

not sure what you mean
I only use prod rn, no staging/dev

K

kian•7/25/23, 5:08 PM

What's your full wrangler.toml?

T

TomatoCakeOP•7/25/23, 5:11 PM

name = "browser-screenshot"
main = "src/worker.js"
compatibility_date = "2023-07-25"
compatibility_flags = [ "nodejs_compat" ]

[placement]
mode = "smart"

browser = { binding = "MYBROWSER", type = "browser" }
kv_namespaces = [
  { binding = "BROWSER_SCREENSHOT_CACHE", id = "xxx" }
]

name = "browser-screenshot"
main = "src/worker.js"
compatibility_date = "2023-07-25"
compatibility_flags = [ "nodejs_compat" ]

[placement]
mode = "smart"

browser = { binding = "MYBROWSER", type = "browser" }
kv_namespaces = [
  { binding = "BROWSER_SCREENSHOT_CACHE", id = "xxx" }
]

name = "browser-screenshot"
main = "src/worker.js"
compatibility_date = "2023-07-25"
compatibility_flags = [ "nodejs_compat" ]

[placement]
mode = "smart"

browser = { binding = "MYBROWSER", type = "browser" }
kv_namespaces = [
  { binding = "BROWSER_SCREENSHOT_CACHE", id = "xxx" }
]

name = "browser-screenshot"
main = "src/worker.js"
compatibility_date = "2023-07-25"
compatibility_flags = [ "nodejs_compat" ]

[placement]
mode = "smart"

browser = { binding = "MYBROWSER", type = "browser" }
kv_namespaces = [
  { binding = "BROWSER_SCREENSHOT_CACHE", id = "xxx" }
]

T

TomatoCakeOP•7/25/23, 5:13 PM

(is the kv id something i have to censor?)

K

kian•7/25/23, 5:16 PM

Nope, but you need to move stuff above

[placement]

[placement]

[placement]

[placement] or change it to be tables as well.

K

kian•7/25/23, 5:17 PM

name = "browser-screenshot"
main = "src/worker.js"
compatibility_date = "2023-07-25"
compatibility_flags = [ "nodejs_compat" ]

[placement]
mode = "smart"

[browser]
binding = "MYBROWSER"

[[kv_namespaces]]
binding = "BROWSER_SCREENSHOT_CACHE"
id = "xxx"

name = "browser-screenshot"
main = "src/worker.js"
compatibility_date = "2023-07-25"
compatibility_flags = [ "nodejs_compat" ]

[placement]
mode = "smart"

[browser]
binding = "MYBROWSER"

[[kv_namespaces]]
binding = "BROWSER_SCREENSHOT_CACHE"
id = "xxx"

name = "browser-screenshot"
main = "src/worker.js"
compatibility_date = "2023-07-25"
compatibility_flags = [ "nodejs_compat" ]

[placement]
mode = "smart"

[browser]
binding = "MYBROWSER"

[[kv_namespaces]]
binding = "BROWSER_SCREENSHOT_CACHE"
id = "xxx"

name = "browser-screenshot"
main = "src/worker.js"
compatibility_date = "2023-07-25"
compatibility_flags = [ "nodejs_compat" ]

[placement]
mode = "smart"

[browser]
binding = "MYBROWSER"

[[kv_namespaces]]
binding = "BROWSER_SCREENSHOT_CACHE"
id = "xxx"

K

kian•7/25/23, 5:17 PM

Basically, since you defined a table (

[placement]

[placement]

[placement]

[placement]) then anything under that until another table or EOF, is under the

[placement]

[placement]

[placement]

[placement] table.

K

kian•7/25/23, 5:17 PM

You basically defined

placement.browser

placement.browser

placement.browser

placement.browser &

placement.kv_namespaces

placement.kv_namespaces

placement.kv_namespaces

placement.kv_namespaces, rather than having top-level

browser

browser

browser

browser and

kv_namespaces

kv_namespaces

kv_namespaces

kv_namespaces keys.

K

kian•7/25/23, 5:18 PM

Using tables (

[browser]

[browser]

[browser]

[browser] and

[[kv_namespaces]]

[[kv_namespaces]]

[[kv_namespaces]]

[[kv_namespaces]]) avoids that.

K

kian•7/25/23, 5:18 PM

If you don't want to use tables for those, just move the

browser

browser

browser

browser and

kv_namespaces

kv_namespaces

kv_namespaces

kv_namespaces lines above

[placement]

[placement]

[placement]

[placement]

T

TomatoCakeOP•7/25/23, 5:19 PM

oh
never used toml before xD

T

TomatoCakeOP•7/25/23, 5:20 PM

ty

T

Tin Cap•7/25/23, 5:25 PM

toml is a silly format IMO

wrangler ignores KV bindings in config

Similar Threads

Similar Threads

Similar Threads