Fix connection string env var precedence over ${file:...} config lookup #4608
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
jeanbisutti
requested review from
harsimar,
rajkumar-rangaraj,
ramthi,
trask and
xiang17
as code owners
jeanbisutti
force-pushed
the
jean/connection-string-file-lookup-precedence
branch
from
e2c1189 to
a40616c
Compare
trask
approved these changes
Feb 3, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #4214.
Using a base applicationinsights.json with
${file:...}across environments (e.g. dev, prod) cannot fall back to the env var in environments where the secret file isn't mounted.The fix defers the file lookup using a
Supplier<String>, so the file is only read when no env var or system property override is present.