BE: Feature - Add support for nested field masking in Kafka UI.#4549
Open
rdossantoslgc wants to merge 1 commit intoprovectus:masterfrom
Open
BE: Feature - Add support for nested field masking in Kafka UI.#4549rdossantoslgc wants to merge 1 commit intoprovectus:masterfrom
rdossantoslgc wants to merge 1 commit intoprovectus:masterfrom
Conversation
Open
2 tasks
Contributor
|
@rdossantoslgc this repo is no longer maintained (#4255), please refer to https://github.com/kafbat/kafka-ui |
Author
|
Error being reported is to do with: fatal error: An error occurred (InvalidAccessKeyId) when calling the ListObjectsV2 operation: The AWS Access Key Id you provided does not exist in our records. Not sure if this is something I can fix myself or the codeowners. |
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.
What changes did you make? (Give an overview)
Problem Solved (Issue reported: #4361)
Previously, the masking feature only supported top-level field names. Users couldn't mask specific nested fields within complex JSON structures, leading to either over-masking (masking entire objects) or under-masking (missing sensitive nested data).
Features Added
Dot Notation: Support for paths like user.email and etc
Pattern Matching: Regex patterns now work with full field paths (e.g., ..secret.)
Array Support: Handles arrays with indexed paths (e.g., users.0.email)
Default Behavior: enableNestedPaths defaults to false
Existing Configs: All current masking configurations continue to work unchanged
No Breaking Changes: API endpoints and data structures remain the same
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)
Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)
Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)