Hi all, I've seen some strange behaviour with environment variables on a Pages project that's using
Hi all,
I've seen some strange behaviour with environment variables on a Pages project that's using next-on-pages.
If I set variables via the Cloudflare dashboard, they show as part of the deployment which is triggered by a direct upload using the cloudflare/wrangler-action@v3 GitHub action. However after adding a page that outputs process.env they're not included in the output, lots of other environment variables are, so the output isn't empty.
If I set environment variables at the step level of a GitHub actions workflow, these are also not carrying through to the deployment.
If I set environment variables at the top level of a GitHub actions workflow, these are carried through to the deployment.
Has anyone else seen similar behaviour?
I've seen some strange behaviour with environment variables on a Pages project that's using next-on-pages.
If I set variables via the Cloudflare dashboard, they show as part of the deployment which is triggered by a direct upload using the cloudflare/wrangler-action@v3 GitHub action. However after adding a page that outputs process.env they're not included in the output, lots of other environment variables are, so the output isn't empty.
If I set environment variables at the step level of a GitHub actions workflow, these are also not carrying through to the deployment.
If I set environment variables at the top level of a GitHub actions workflow, these are carried through to the deployment.
Has anyone else seen similar behaviour?
