Disable $$ expansion for backward compatibility with old versions #5134
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
dmitryax
force-pushed
the
remove-double-dollar-fg
branch
from
9cd7208 to
b483411
Compare
dmitryax
force-pushed
the
remove-double-dollar-fg
branch
from
b483411 to
8007585
Compare
jvoravong
approved these changes
Jul 24, 2024
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.
Stop expanding environment variables starting with $$ in configuration files. This behavior was introduced in v0.42.0 to support a bug causing double expansion.
SPLUNK_DOUBLE_DOLLAR_CONFIG_SOURCE_COMPATIBLEcontrolling this behavior is removed now.$$is now treated as an escape sequence representing a literal $ character.