backport to 1.31: rds: normalize rds provider's config before calculating hash (#37180) #37844
Conversation
This file contains 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
…oxy#37180) Signed-off-by: Christoph Pakulski <[email protected]>
ravenblackx
approved these changes
Dec 31, 2024
cpakulski
added a commit
to cpakulski/envoy
that referenced
this pull request
Dec 31, 2024
…ting hash (envoyproxy#37180) (envoyproxy#37844) Backport envoyproxy#37180 to release 1.31 Additional Description: This is not a security fix, but affects certain users and requires expensive work-around. Identical to backport to 1.32: envoyproxy#37749 Risk Level: Low Testing: Added unit test Docs Changes: No Release Notes: Yes Platform Specific Features: No Runtime guard: Yes Signed-off-by: Christoph Pakulski <[email protected]>
|
Thanks @ravenblackx ! |
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.
Backport #37180 to release 1.31
Additional Description:
This is not a security fix, but affects certain users and requires expensive work-around.
Identical to backport to 1.32: #37749
Risk Level: Low
Testing: Added unit test
Docs Changes: No
Release Notes: Yes
Platform Specific Features: No
Runtime guard: Yes