Skip to content

Commit 122bc84

Browse files
WeltraumschafJ12934
authored andcommitted
#2287 Fix Admonition in Post-Processing Hooks How-To
Signed-off-by: Sven Strittmatter <sven.strittmatter@iteratec.com>
1 parent 72413ae commit 122bc84

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

documentation/docs/how-tos/hooks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ In principle, the _secureCodeBox_ works in such a way that the _raw findings_ (t
1818

1919
The basic purpose is to transfer the findings to third-party systems. Findings can be read with a _ReadHook_ and processed further as required (e.g. saved in another system via a REST call). On the other hand, _ReadWriteHooks_ also offer the option of adding further information to Findings or modifying them.
2020

21-
::: Caution
21+
:::caution
2222
In principle, both the _raw findings_ and the _secureCodeBox findings_ are available to hooks via API. In principle, the uniformed _secureCodeBox findings_ should be preferred. However, the [DefectDojo persistence hook](/docs/hooks/defectdojo/), for example, only processes the _raw findings_. This means that post-processing hooks that work on the _secureCodeBox finding_ have no effect on the data that ends up in DefectDojo.
2323

2424
This means that depending on what you want to achieve with your hook, you need to look at how the following hooks process the findings.

0 commit comments

Comments
 (0)