Can we have an option to let worker's build variables and secrets extend the runtime ones?
When environment variables are misconfigured in production, it is really hard to debug since it only throws a 500 Error without detailed info. Currently, I'm using @t3-oss/env-core to validate my env variables, and I want to process it during the build time. However, right now I have to manually add those runtime variables and secrets in the build config, since it cannot get runtime ones. I'm wondering if you can give an option to extend the runtime variables? Because even if I can manually add those twice, I don't think it is a good practice to maintain in the future. Or if I got it wrong and there are better approaches to solve my issue, please let me know.
0 Replies