local development with secrets

Question

I am following this guide to get secrets added to my prod environment with cloudflare workers:
https://developers.cloudflare.com/workers/platform/environment-variables/#comparing-secrets-and-environment-variables

I am able to add new secrets via wrangler secret put, and I see them in the dashboard. When I run my code locally with wrangler, it doesn't look like the variables are injected. I'm getting an error like this:

Uncaught ReferenceError: TOKEN is not defined
  at line 0

    at throwFetchError (/Users/justin.beckwith/.nvm/versions/node/v16.14.0/lib/node_modules/wrangler/wrangler-dist/cli.js:134316:17)
    at fetchResult (/Users/justin.beckwith/.nvm/versions/node/v16.14.0/lib/node_modules/wrangler/wrangler-dist/cli.js:134287:5)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async previewToken (/Users/justin.beckwith/.nvm/versions/node/v16.14.0/lib/node_modules/wrangler/wrangler-dist/cli.js:134658:29)
    at async createWorker (/Users/justin.beckwith/.nvm/versions/node/v16.14.0/lib/node_modules/wrangler/wrangler-dist/cli.js:134675:17)
    at async start (/Users/justin.beckwith/.nvm/versions/node/v16.14.0/lib/node_modules/wrangler/wrangler-dist/cli.js:136075:16) {

I know the secret is set, and from what I can tell the values should be auto-injected. Any ideas on what I'm missing here? Thank you!

Did you find out how to make this work by any chance? Both answers provided work for normal environment variables defined in `wrangler.toml`, but it does not automatically inject the secrets I put via `wrangler secret put`. — Torsten Engelbrecht, Oct 07 '22 at 07:07

Tom · Accepted Answer · 2023-01-04T10:35:51.090

I got the answer from here. You can create the file named .dev.vars, and put the secrets in file. Wrangler 2 will auto binding when you use the command $ wrangler dev

example:

put the secret in .dev.vars files

API_KEY_0 = "YOU_SECRET_0"
API_KEY_1 = "YOU_SECRET_1"

run the command below and you can see this in terminal.

$ wrangler dev

...

Your worker has access to the following bindings:
- Vars:
  - API_KEY_0: "(hidden)"
  - API_KEY_1: "(hidden)"

...

you code in .ts or .js

interface Env {
  API_KEY_0: string
  API_KEY_1: string
}

export default {
  async fetch(request: Request, env: Env, context: ExecutionContext): Promise<Response> {
    console.log(env.API_KEY_0, env.API_KEY_1)
  }
}

export default {
  async fetch(request, env, context) {
    console.log(env.API_KEY_0, env.API_KEY_1)
  }
}

for your reference

So the secrets only work when we deployed them only? if we want it to inject to normal env context we really have to create the .dev.vars? — Thiti-Dev, Jan 08 '23 at 09:06

score 1 · Answer 2 · answered May 15 '22 at 18:42

1

To expand on melops answer above in Typescript:

interface Env {
  var_name: var_type
}

export default {
  async fetch(request: Request, env: Env, context: ExecutionContext): Promise<Response> {
    console.log(env);
  },
};

answered May 15 '22 at 18:42

Bram Adams

63
1
8

1

he is using javascript – Ramsey Nov 18 '22 at 20:53

score 0 · Answer 3 · answered Mar 17 '22 at 14:03

0

If you are using Module Workers you should be able to access your secrets via env.

export default {
    async fetch(request, env, context) {
      return new Response(`TOKEN: ${env.TOKEN}`)
    }
}

I am currently using wrangler2 version 0.0.17

answered Mar 17 '22 at 14:03

melops

11
2

score 0 · Answer 4 · answered Jul 05 '23 at 16:04

0

Thanks to Tom, my problem was solved by using the .dev.var file and declaring the SECRET KEYS in the Env interface.

answered Jul 05 '23 at 16:04

Naser Papi

21
5

local development with secrets

4 Answers4