This repository was archived by the owner on Mar 23, 2026. It is now read-only.
Cfn: Fix backslash processing for dynamic replacement values#13212
Merged
Cfn: Fix backslash processing for dynamic replacement values#13212
Conversation
Test Results - Alternative Providers575 tests 330 ✅ 25m 34s ⏱️ Results for commit ff83a05. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 39m 5s ⏱️ Results for commit ff83a05. |
pinzon
approved these changes
Sep 30, 2025
Member
pinzon
left a comment
There was a problem hiding this comment.
LGTM. Thank you for the fix and catching the error with the LOG
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
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.
Motivation
When dynamic references (like
{{resolve:secretsmanager:secret-id:secret-string:json-key::}}) return backslashes, they are currently not handled correctly. Mainly, they are interpreted byre.sub, and used to escape characters (or reference sections of the regex match).The python documentation says this about this topic:
This leads to issues if the secret contains one or multiple backslashes, leading either to escape errors (
bad escape \<something> at position <something>or changed values (\\->\,\&->&).This can lead to significant, but hard to debug issues.
The change replaces the string with a function returning a string, as the backslashes are not processed:
Changes
legacyinstead ofengine-legacy).