refactor: split spec_cleaner to multiple sub-modules #4324
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.
This is a preparation for IPv6 and MAC address obfuscation. By splitting it to multiple sub-modules, it will be easy for adding new modules, e.g. IPv6 and MAC obfuscation. Jira: RHINENG-15077
get_obfuscate_functions
with a new keyword argumentwidth
, for specs that need to keep the original words width, thiswidth
needs to be set by hand before content cleaning. In the future, it will be moved to the RegistryPoint for user to set by hand per specs.password value
and specifiedkeywords
to kind of fixed strings/words, so moved it to the obfuscation module. User can exclude it by specifying it with, e.g. "no_obfuscate=['password']" while adding its RegistryPoint ininsights.specs.Specs
. Jira: RHINENG-14756All Pull Requests:
Check all that apply:
Complete Description of Additions/Changes:
Add your description here