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
I'm running a supported version of the application which is listed here and the feature is not present there
Is your proposal related to a problem?
It is possible to mask fields of a message by field name.
If you have a huge number of fields (say >1000), it is not possible to mask all fields together and just exclude (whitelist) specific fields from the masking.
Describe the feature you're interested in
For messages with a huge number of fields it would be great to be able to mark all fields for masking and whitelist some of the fields that should be excluded from masking. Otherwise each single field has to be configured for masking to be able to leave some out.
Describe alternatives you've considered
At the moment this could only be done by configuring each single field of a message for being masked or unmasked.
Version you're running
0.7.1
Additional context
Thanks a lot for your great contributions!
The text was updated successfully, but these errors were encountered:
Issue submitter TODO list
Is your proposal related to a problem?
It is possible to mask fields of a message by field name.
If you have a huge number of fields (say >1000), it is not possible to mask all fields together and just exclude (whitelist) specific fields from the masking.
Describe the feature you're interested in
For messages with a huge number of fields it would be great to be able to mark all fields for masking and whitelist some of the fields that should be excluded from masking. Otherwise each single field has to be configured for masking to be able to leave some out.
Describe alternatives you've considered
At the moment this could only be done by configuring each single field of a message for being masked or unmasked.
Version you're running
0.7.1
Additional context
Thanks a lot for your great contributions!
The text was updated successfully, but these errors were encountered: