Clarify how wrangler --env affects loading .env and .dev.vars
#19340
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vicb
requested review from
a team,
GregBrimble,
ToriLindsay,
WalshyDev,
irvinebroque and
mikenomitch
as code owners
github-actions
bot
assigned
irvinebroque,
ToriLindsay,
GregBrimble,
mikenomitch and
WalshyDev
Deploying cloudflare-docs with
|
| Latest commit: |
9298939
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9b273a98.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://envarg.cloudflare-docs-7ou.pages.dev |
Contributor
|
Files with changes (up to 15)
|
petebacondarwin
approved these changes
Jan 22, 2025
Contributor
petebacondarwin
left a comment
petebacondarwin
left a comment
There was a problem hiding this comment.
Should we explicitly call out that we do not combine the vars from .env.<env-name> with those in .env?
Contributor
Author
I think it would be a great idea, can you add this as a suggestion - your english is better than mine :) |
src/content/docs/workers/wrangler/system-environment-variables.mdx
Outdated
Show resolved
Hide resolved
….mdx Co-authored-by: Pete Bacon Darwin <[email protected]>
vicb
commented
Jan 22, 2025
petebacondarwin
approved these changes
Jan 22, 2025
Contributor
Author
|
@ToriLindsay can you please take a look when you have time? 🙏 |
ToriLindsay
approved these changes
Jan 28, 2025
|
|
||
| :::note | ||
|
|
||
| You can set system environment variables per environment by creating additional files with the naming convention `.env.<environment-name>`. When you set the environment using `wrangler <command> --env <environment-name>`, such an environment specific file will be loaded instead of the `.env` file - they are not merged. |
Contributor
There was a problem hiding this comment.
Suggested change
| You can set system environment variables per environment by creating additional files with the naming convention `.env.<environment-name>`. When you set the environment using `wrangler <command> --env <environment-name>`, such an environment specific file will be loaded instead of the `.env` file - they are not merged. | |
| To set different system environment variables for each environment, create files named `.env.<environment-name>`. When you use `wrangler <command> --env <environment-name>`, the corresponding environment-specific file will be loaded instead of the `.env` file, so the two files are not merged. |
| ``` | ||
|
|
||
| You can set secrets per environment by creating additional files with the naming convention `.dev.vars.<environment-name>`. Like other environment variables, secrets are [non-inheritable](/workers/wrangler/configuration/#non-inheritable-keys) and must be defined per environment. | ||
| You can set secrets per environment by creating additional files with the naming convention `.dev.vars.<environment-name>`. When you set the environment using `wrangler <command> --env <environment-name>`, such an environment specific file will be loaded instead of the `.dev.vars` file - they are not merged. |
Contributor
There was a problem hiding this comment.
Suggested change
| You can set secrets per environment by creating additional files with the naming convention `.dev.vars.<environment-name>`. When you set the environment using `wrangler <command> --env <environment-name>`, such an environment specific file will be loaded instead of the `.dev.vars` file - they are not merged. | |
| To set different secrets for each environment, create files named `.dev.vars.<environment-name>`. When you use `wrangler <command> --env <environment-name>`, the corresponding environment-specific file will be loaded instead of the `.dev.vars` file, so the two files are not merged. |
vicb
added a commit
that referenced
this pull request
Jan 28, 2025
vicb
added a commit
that referenced
this pull request
Jan 28, 2025
deadlypants1973
pushed a commit
that referenced
this pull request
Jan 29, 2025
…19340) Co-authored-by: Pete Bacon Darwin <[email protected]>
deadlypants1973
pushed a commit
that referenced
this pull request
Jan 29, 2025
kodster28
pushed a commit
that referenced
this pull request
Jan 30, 2025
…19340) Co-authored-by: Pete Bacon Darwin <[email protected]>
kodster28
pushed a commit
that referenced
this pull request
Jan 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Clarify how
wrangler --envaffects loading.envand.dev.varsRelated to cloudflare/workers-sdk#7859
Documentation checklist