-
Notifications
You must be signed in to change notification settings - Fork 0
Move AUTH_TOKEN to .dev.vars and update README with instructions for setting AUTH_TOKEN secret
#2
Conversation
…ctions for AUTH_TOKEN usage
a6fb91b to
3dff18b
Compare
AUTH_TOKEN to `.dev.vars and update README with instructions for setting AUTH_TOKEN secretAUTH_TOKEN to .dev.vars and update README with instructions for setting AUTH_TOKEN secret
| @@ -0,0 +1 @@ | |||
| AUTH_TOKEN="your-secret-token-here" No newline at end of file | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit but maybe we could make this OTEL_WORKER_AUTH_TOKEN to make it more explicit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah wait, realizing this will require a more substantial change throughout the code, so feel free to disregard
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think this is also making it quite verbose, specially since these envvars are scoped to a single app
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing it to a secret also requires the code to fetch it from the secret and not var
changed! |
|
deployed and tested with https://brett-otel-worker.fp.dev, going to merge |
Made a few small tweaks to how the
AUTH_TOKENis set, and updated the README accordingly.Since
wrangler.tomlis checked into version control, it's recommended to put secrets in.dev.varsfor developing locally, and then set the secret for the worker vianpx wrangler secret put NAME_OF_SECRET.This also prevents the
[vars]inwrangler.tomlfrom clobbering any runtime variables you set manually when you go to deploy.