cosmic jetty
I have a worker that has both variables and secrets in the "Settings" panel for Worker Builds. In production builds everything's fine, but in preview builds, secrets appear empty. To check that I added an env call before builds and logging in the js code. This is what I see:
API_BASEURL=https://****/api/
API_SECRET_KEY=
...
Error: Invalid baseUrl or secretKey ("https://****/api/", "")
What can I do?
nova salmon
Can you share your wrangler config and you deploy command?
cosmic jetty
can I send you the wrangler.toml privately?
nova salmon
Can you redact? I'm mostly interested in your environments config and non production deploy command
cosmic jetty
the build command is:
curl https://ipinfo.io/ip ; env ; pnpm run cf-build
the preview deploy command is:
pnpm run deploy --env staging
(without --env staging in the production case)
cosmic jetty
Can you redact? I'm mostly interested in your environments config and non produc...
ok
nova salmon
Gotcha, and your staging Worker, can you see if your Worker has the vars set in dash?
cosmic jetty
this is the wrangler.toml
cosmic jetty
Gotcha, and your staging Worker, can you see if your Worker has the vars set in ...
I have build variables and secrets, "run environment" variables set through wrangler.toml and "run environment" secrets set through the settings page
the API_SECRET_KEY is set both in build secrets and in "run environment" secrets, or the production build would fail
nova salmon
You want these in "variables and secrets" in the Worker settings
alternatively wrangler secret put --env staging API_SECRET_KEY
cosmic jetty
alternatively wrangler secret put --env staging API_SECRET_KEY
oh, that is interesting... is there an equivalent for the worker builds secrets?
API_SECRET_KEY is used by next during build to get data for prebuilding pages
nova salmon
Honestly I'm not sure up to date on Workers CI (not on that team) that I wouldn't be able to tell ya 😅 . I think you want that as a regular variable for use during your app build
cosmic jetty
maybe I'm beginning to understand something... using environments creates automatically a new "worker" with the original name "-environment", but since my build fails that still doesn't exist, so I cannot set build secrets... am I right?
cosmic jetty
Honestly I'm not sure up to date on Workers CI (not on that team) that I wouldn'...
I see... I'm really grateful you took time to answer! Can you refer me to someone who could have more insights?
nova salmon
maybe I'm beginning to understand something... using environments creates automa...
That seems reasonable, but also a little confused because if you have this as a workers CI variable then I think that should work? Generally speaking the team pops in on Discord from time to time, but it's all on a volunteer basis. I can't promise that you'll get a response from that team, but I can forward along!
warm oasis