[release/9.4] Ensure all YARP env vars are strings #10435
Merged
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
There are expectations in other integrations that primitive environment variables are serialized to strings and not random objects like enums and bools. Fix #10432
dotnet-policy-service
bot
added
Re-opened Github-Action PR
and removed
Closed Github-Action PR
labels
davidfowl
approved these changes
Jul 15, 2025
joperezr
reviewed
Jul 15, 2025
joperezr
approved these changes
Jul 15, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #10434 to release/9.4
/cc @eerhardt
Customer Impact
When someone uses YARP and an Azure resource in the same app, it fails to run or publish.
Testing
Added a new test to ensure all env vars are strings.
Risk
Minimal - only affects YARP, which is new, in preview, and is isolated from everything else.
Regression?
No