Best practices for customizing a TKU discovery pattern |
This option implies that the TKU OOTB runs and the custom pattern modifies the scan result afterwards. The option 1 and 2 are suitable in the same cases.
This options was discussed in this community post. Extracts: Peter> ... running the TKU's "as is" and then customize this with patterns on top
Peter> ... yes you can! Via importing the original module patterns and then declaring the requires in the overview section Option 3: Leave the TKU as it is and activate a new custom pattern that overrides one of the TKU patterns.
This option is suitable when the way the TKU patterns work has to be deeply changed. For example:
With this option, the custom pattern replaces the TKU pattern. The behaviors of the overriden and custom patterns may diverge and it could lead to issues.
Note that when the upgrade will deploy bug fixes and new features in the overriden pattern, it have will no effect on the custom overriding pattern. This imply some maintenance activity to manually merge the improvements from the overriden pattern into the custom overriding pattern. This options was discussed in this community post. Extracts: Philippe > ... if you want to modify a TKU named "PatternA", keep the TKU as it is, copy/paste patternA into a custom pattern, name it patternA_custom and say "overrides patternA" [ and modify the custom overriding pattern as you like]
Option 4: (not recommended) Edit an existing TKU pattern (no new pattern added) Pros: This option is relatively quick. No conflict risks at the next TKU upgrade.
Cons: TKU upgrades may overwrite the customized pattern. This imply some maintenance activity to backup the custom pattern, restore it when needed and manually merge the improvements from the overriden pattern into the custom pattern.
Option 5: (not recommended) Deactivate a TKU pattern and replace it with a customized copy of the original pattern (with a different name) Pros: The next TKU upgrade won't overwrite the custom pattern Cons: The deactivation of TKU patterns may not be possible because of dependency issues. Next TKU upgrades will reactivate the deactivated TKU pattern and may modify it. This imply some maintenance activity to deactivate the TKU pattern after each upgrade and manually merge the changes from the deactivated into the custom pattern. |