stack/apps
Aman Ganapathy 45df7518c3
[Refactor] Rework Environment Variable Checks in Email-Rendering Pipeline (#1161)
### Context
Via the email-monitor and sentry traces, we found out that we were
running the "without fallback" path in production. This was because the
right environment variables weren't populated in Vercel, but it exposed
how our system let this slide. This occurred because the check we did
for fallback vs non-fallback routes relied on checking whether a certain
environment variable was empty.

### Summary of Changes
We now use a sentinel value for the check instead of an empty value.
Additionally, we remove default values from the `getEnvVariable` checks
to ensure they throw if not populated. We also guard against the
sentinel value being used in production

### Config Changes
We need to update and make sure the vercel sandbox environment variables
are populated in production.
2026-02-04 16:54:18 -08:00
..
backend [Refactor] Rework Environment Variable Checks in Email-Rendering Pipeline (#1161) 2026-02-04 16:54:18 -08:00
dashboard Test sign-up rules widget 2026-02-04 11:22:42 -08:00
dev-launchpad chore: update package versions 2026-02-04 10:01:04 -08:00
e2e Test sign-up rules widget 2026-02-04 11:22:42 -08:00
mock-oauth-server chore: update package versions 2026-02-04 10:01:04 -08:00
oauth-mock-server In-source unit tests (#429) 2025-02-14 11:47:52 -08:00