fix: apply config.env before ${VAR} substitution #1813
Closed
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
envsection values are available during${VAR}substitutionresolveConfigEnvVars()ran beforeapplyConfigEnv(), causing "Missing env var" errors for vars defined in configProblem
When config has:
{ "env": { "MINIMAX_API_KEY": "sk-..." }, "models": { "providers": { "minimax": { "apiKey": "${MINIMAX_API_KEY}" } } } }The substitution failed because the
envsection wasn't applied toprocess.envyet.Test plan