Why is [vars] setting my production variables instead of [env.production.vars]?

R

Register•4/28/24, 6:22 PM

I want to be able to have local env variables when I run wrangler dev locally and it seems to use [vars]. Documentation specified env.production.vars

R

Register•4/28/24, 6:29 PM

https://developers.cloudflare.com/pages/functions/wrangler-configuration/#environment-specific-overrides

Cloudflare Docs

Configuration · Cloudflare Pages docs

Pages Functions can be configured two ways, either via the Cloudflare dashboard or wrangler.toml, a configuration file used to customize the …

R

Register•4/28/24, 6:29 PM

name = "my-pages-site"
pages_build_output_dir = "./dist"

[[kv_namespaces]]
binding = "KV"
id = "<NAMESPACE_ID>"

[vars]
API_KEY = "1234567asdf"

[[env.preview.kv_namespaces]]
binding = "KV"
id = "<PREVIEW_NAMESPACE_ID>"

[env.preview.vars]
API_KEY = "8901234bfgd"

name = "my-pages-site"
pages_build_output_dir = "./dist"

[[kv_namespaces]]
binding = "KV"
id = "<NAMESPACE_ID>"

[vars]
API_KEY = "1234567asdf"

[[env.preview.kv_namespaces]]
binding = "KV"
id = "<PREVIEW_NAMESPACE_ID>"

[env.preview.vars]
API_KEY = "8901234bfgd"

name = "my-pages-site"
pages_build_output_dir = "./dist"

[[kv_namespaces]]
binding = "KV"
id = "<NAMESPACE_ID>"

[vars]
API_KEY = "1234567asdf"

[[env.preview.kv_namespaces]]
binding = "KV"
id = "<PREVIEW_NAMESPACE_ID>"

[env.preview.vars]
API_KEY = "8901234bfgd"

name = "my-pages-site"
pages_build_output_dir = "./dist"

[[kv_namespaces]]
binding = "KV"
id = "<NAMESPACE_ID>"

[vars]
API_KEY = "1234567asdf"

[[env.preview.kv_namespaces]]
binding = "KV"
id = "<PREVIEW_NAMESPACE_ID>"

[env.preview.vars]
API_KEY = "8901234bfgd"

R

Register•4/28/24, 6:30 PM

[vars] treated as production vars but also used for the local dev

R

Register•4/28/24, 6:30 PM

if I am testing on local dev then why would I want to use production secrets???

R

Register•4/28/24, 6:33 PM

R

Register•4/28/24, 6:33 PM

i have an API that prints the value of STAGE. This is running locally

R

Register•4/28/24, 6:34 PM

this is

but when I delpoy, Pages uses [vars] for my production instead of [env.production.vars]

C

Coolio85•4/28/24, 10:34 PM

For local development I'm pretty sure you use a

.dev.vars

.dev.vars

.dev.vars

.dev.vars file with the values inside there

J

jculveyhouse•4/29/24, 3:04 PM

Also if these are actual secrets, you may want to consider using secrets (e.x.

wrangler secret put API_KEY

wrangler secret put API_KEY

wrangler secret put API_KEY

wrangler secret put API_KEY) instead of environment variables: https://developers.cloudflare.com/pages/functions/bindings/#secrets

Like Coolio mentions,

.dev.vars

.dev.vars

.dev.vars

.dev.vars would be used for local dev in that case

Cloudflare Docs

Bindings · Cloudflare Pages docs

A binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions …

CCoolio85 For local development I'm pretty sure you use a `.dev.vars` file with the values...

R

Register•5/2/24, 12:02 PM

[env.dev.vars]
STAGE = "local"

[env.preview.vars]
STAGE = "preview"

[env.production.vars]
STAGE = "production"

[env.dev.vars]
STAGE = "local"

[env.preview.vars]
STAGE = "preview"

[env.production.vars]
STAGE = "production"

[env.dev.vars]
STAGE = "local"

[env.preview.vars]
STAGE = "preview"

[env.production.vars]
STAGE = "production"

[env.dev.vars]
STAGE = "local"

[env.preview.vars]
STAGE = "preview"

[env.production.vars]
STAGE = "production"

R

Register•5/2/24, 12:04 PM

Ah I see it's a file.

R

Register•5/2/24, 12:04 PM

ok that worked

RRegister ``` [env.dev.vars] STAGE = "local" [env.preview.vars] STAGE = "preview" [env.p...

H

Hello, I’m Allie!•5/2/24, 12:57 PM

Note too that by default, there isn't an environment at all. You have to explicitly tell it to use the production environment

H

Hello, I’m Allie!•5/2/24, 12:57 PM

Or any other environment

HHello, I’m Allie!Note too that by default, there isn't an environment at all. You have to explici...

R

Register•5/2/24, 1:16 PM

I am doing that, here right?

RRegister I am doing that, here right?

H

Hello, I’m Allie!•5/2/24, 1:20 PM

Where?

H

Hello, I’m Allie!•5/2/24, 1:20 PM

Oh

H

Hello, I’m Allie!•5/2/24, 1:21 PM

Wait

H

Hello, I’m Allie!•5/2/24, 1:21 PM

Pages

H

Hello, I’m Allie!•5/2/24, 1:21 PM

H

Hello, I’m Allie!•5/2/24, 1:21 PM

I'm not actually sure what environment

pages dev

pages dev

uses...

RRegister I am doing that, here right?

H

Hello, I’m Allie!•5/2/24, 1:26 PM

It looks like by default

pages dev

pages dev

only uses top-level keys

H

Hello, I’m Allie!•5/2/24, 1:26 PM

So any environment-scoped vars won't be applied.

H

Hello, I’m Allie!•5/2/24, 1:27 PM

You may be able to apply an environment with

--environment

--environment

--environment

--environment

R

Register•5/2/24, 1:40 PM

Looks like the .dev.vars file is working out for me

R

Register•5/2/24, 1:40 PM

and the other configs

[env.preview.vars]
STAGE = "preview"

[env.production.vars]
STAGE = "production"

[env.preview.vars]
STAGE = "preview"

[env.production.vars]
STAGE = "production"

[env.preview.vars]
STAGE = "preview"

[env.production.vars]
STAGE = "production"

[env.preview.vars]
STAGE = "preview"

[env.production.vars]
STAGE = "production"

are doing their job as I expected them too

R

Register•5/2/24, 1:40 PM

I did notice [vars] works when I use [env.production.vars] with it

R

Register•5/2/24, 1:40 PM

otherwise [vars] defaults to [env.production.vars] - Which I think is kinda silly but w/e

R

Register•5/2/24, 1:41 PM

Appreciate the feedback guys!

R

Register•5/2/24, 1:41 PM

I got everything I needed

Why is [vars] setting my production variables instead of [env.production.vars]?

Similar Threads

Similar Threads

Similar Threads