Why is [vars] setting my production variables instead of [env.production.vars]?
Original message was deleted
RI 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
RCloudflare Docs
Pages Functions can be configured two ways, either via the Cloudflare dashboard or wrangler.toml, a configuration file used to customize the …
RR[vars] treated as production vars but also used for the local dev
Rif I am testing on local dev then why would I want to use production secrets???
RRi have an API that prints the value of STAGE. This is running locally
Rthis is 
but when I delpoy, Pages uses [vars] for my production instead of [env.production.vars]
but when I delpoy, Pages uses [vars] for my production instead of [env.production.vars]
CFor local development I'm pretty sure you use a
.dev.vars
JAlso if these are actual secrets, you may want to consider using secrets (e.x.
Like Coolio mentions,
wrangler secret put API_KEYLike Coolio mentions,
.dev.varsCloudflare Docs
A binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions …
RAh I see it's a file.
Rok that worked
HNote too that by default, there isn't an environment at all. You have to explicitly tell it to use the production environment
HOr any other environment
RI am doing that, here right?
HWhere?
HOh
HWait
HPages
H
HI'm not actually sure what environment
pages devIt looks like by default
pages devSo any environment-scoped vars won't be applied.
HYou may be able to apply an environment with
--environmentLooks like the .dev.vars file is working out for me
Rand the other configs
are doing their job as I expected them too
are doing their job as I expected them too
RI did notice [vars] works when I use [env.production.vars] with it
Rotherwise [vars] defaults to [env.production.vars] - Which I think is kinda silly but w/e
RAppreciate the feedback guys!
RI got everything I needed
