You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It's up for debate if this is a bug, but at least it is unexpected behaviour to me and I can't find it in the documentation. So filed a bug report anyway.
When configuring multiple ValueMaskers. and both of them would match a certain value, on the first one is applied.
To Reproduce
Steps to reproduce the behavior:
Assuming we have two net.logstash.logback.mask.ValueMaskers:
com.example.MatchesOnStringA which would mask all occurences of "StringA" to "*******"
com.example.MatchesOnStringB which would mask all occurences of "StringB" to "*******"
Previously, masking of a single value would stop after the first ValueMasker returned a masked value.
This meant that only one ValueMasker would process a string.
Now, all ValueMaskers are given the opportunity to process a value, which means that multiple substrings can be masked independently by different ValueMaskers
Fixes#690
* Allow masking of multiple substrings
Previously, masking of a single value would stop after the first ValueMasker returned a masked value.
This meant that only one ValueMasker would process a string.
Now, all ValueMaskers are given the opportunity to process a value, which means that multiple substrings can be masked independently by different ValueMaskers
Fixes#690
Describe the bug
It's up for debate if this is a bug, but at least it is unexpected behaviour to me and I can't find it in the documentation. So filed a bug report anyway.
When configuring multiple
ValueMasker
s. and both of them would match a certain value, on the first one is applied.To Reproduce
Steps to reproduce the behavior:
net.logstash.logback.mask.ValueMasker
s:com.example.MatchesOnStringA
which would mask all occurences of"StringA"
to"*******"
com.example.MatchesOnStringB
which would mask all occurences of"StringB"
to"*******"
logback.xml
configuration†:† this is maybe not entirely correct configuration, I've manually trimmed a few lines here and there to make it consise
Expected behavior
I would expect this to match
But in fact only the first configured
ValueMasker
is applied, so the result isAdditional context
I had a look through the sources and I guess it's to be expected because of this code:
The text was updated successfully, but these errors were encountered: