Skip to content

[docs]: Clarify astro:env/server variable evaluation and secret handling #12818

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Dec 4, 2025
Merged

[docs]: Clarify astro:env/server variable evaluation and secret handling #12818

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
2da8c15
feat(docs): Clarify astro:env/server variable evaluation and secret h…
fkatsuhiro Dec 2, 2025
87b6867
fix: move explanation location and add sample commands
fkatsuhiro Dec 3, 2025
58866e1
fix: sample secret server valiable placeholder to dummy
fkatsuhiro Dec 3, 2025
f0f13ac
fix: remove translation other than English
fkatsuhiro Dec 3, 2025
e0ffd59
integrate new info into existing text
sarah11918 Dec 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion src/content/docs/en/guides/environment-variables.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -279,7 +279,9 @@ There are three kinds of environment variables, determined by the combination of
import { API_SECRET } from "astro:env/server";
```

By default, secrets are only validated at runtime. You can enable validating private variables on start by [configuring `validateSecrets: true`](/en/reference/configuration-reference/#envvalidatesecrets).
By default, all secrets are validated whenever anything is imported from the `astro:env/server` module. This means, secrets may be validated even when they are not imported. You may need to [pass dummy environment variables](#setting-environment-variables) to satisfy this validation during the build.

You can also enable validating secrets on start by [configuring `validateSecrets: true`](/en/reference/configuration-reference/#envvalidatesecrets).

:::note
**Secret client variables** are not supported because there is no safe way to send this data to the client. Therefore, it is not possible to configure both `context: "client"` and `access: "secret"` in your schema.
Expand Down