Open jjjrmy opened 3 months ago
I think this could be solved if the Pages build infrastructure simply provided the CLOUDFLARE_ACCOUNT_ID
environment variable when running the Wrangler commands. I believe that the account is already known at this point and so could be made available.
Allowing the wrangler.toml
to specify the account_id
could create potential for a source of truth conflict where the Pages infrastructure is running within one account but then Wrangler is trying to deploy to another account.
@petebacondarwin it does fix it by adding the CLOUDFLARE_ACCOUNT_ID
as an environment variable.
I'm just following the directions as per the console error suggestions. And yes I think it should know already what account is in it.
Yeah the error message is the most unfortunate piece here but I do think that Pages CI can just do this for us and avoid the user having to do anything.
Which Cloudflare product(s) does this pertain to?
Workers Runtime
What version(s) of the tool(s) are you using?
3.70.0 [wrangler]
What version of Node are you using?
No response
What operating system and version are you using?
Cloudflare Dashboard
Describe the Bug
https://dash.cloudflare.com/ab7347813b21ea6079df4cb18c4bb9e8/pages/view/exchange-traded-fund/952e6991-3192-47dd-9121-12b7bbce5d01
https://dash.cloudflare.com/ab7347813b21ea6079df4cb18c4bb9e8/pages/view/exchange-traded-fund/caf73d0b-3b79-4c19-9ce6-e83e33dac0f4
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response