You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I'm integrating a Cloudflare Pages application in combination with Worker functions which are connecting to a unique branch of my Postgres Database (using Neon).
However, what I noticed is that there's currently no functionality available to set environment variables (secrets) scoped to my unique preview deployment.
Cloudflare console does not mark these variables as sensitive/secret, but instead outputs them in the UI (especially concerning since it's database credentials).
This works to some extent in the wrangler.toml, however when you start introducing environments (e.g. [env.dev]) appending the variables at the end of the wrangler.toml may set the variables for the wrong environment.
Would like to hear if it's an oversight from my end and/or if there's any future plans on supporting this behavior. Thanks!
The text was updated successfully, but these errors were encountered:
Hi!
Currently I'm integrating a Cloudflare Pages application in combination with Worker functions which are connecting to a unique branch of my Postgres Database (using Neon).
However, what I noticed is that there's currently no functionality available to set environment variables (secrets) scoped to my unique preview deployment.
My setup for deploying from Github Actions is very similar to the following example: https://github.com/neondatabase/preview-branches-with-cloudflare/blob/main/.github/workflows/deploy-preview.yml#L42. What i noticed is that they explicitly set the
DATABASE_URL
in thewrangler.toml
.The downsides of this however:
wrangler.toml
, however when you start introducing environments (e.g.[env.dev]
) appending the variables at the end of thewrangler.toml
may set the variables for the wrong environment.Would like to hear if it's an oversight from my end and/or if there's any future plans on supporting this behavior. Thanks!
The text was updated successfully, but these errors were encountered: