Repository navigation
IGNITE-29155 Fix sensitive data exposure and cyclic reference handling in ConfigurationView - #13726
Merged
Merged
Conversation
shishkovilja
force-pushed
the
ignite-29155
branch
from
October 22, 2026 14:17
71387f3 to
c365aea
Compare
…g in ConfigurationView
shishkovilja
force-pushed
the
ignite-29155
branch
from
October 23, 2026 06:35
4ca0a7b to
bc6af9f
Compare
NSAmelchev
approved these changes
Oct 26, 2026
Contributor
TCBot Test Analysis
Possible Blockers (0)No blockers found. New Tests (3)
|
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 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.
SYS.CONFIGURATION. Only whenIGNITE_TO_STRING_INCLUDE_SENSITIVE=false.@SensitivePropertyannotation for configuration getters.char[]properties are treated as sensitive automatically.StackOverflowError.nullarray elements no longer causeNullPointerException.