Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Create parser-documentation-template.md * add additional line to how-to-write-a-parser.md * Update how-to-write-a-parser.md * add to unittests for parser * correct linting error --------- Co-authored-by: Paul Osinski <paul.m.osinski@gmail.com>
- Loading branch information
1 parent
c8d6aed
commit 462c9a3
Showing
3 changed files
with
39 additions
and
2 deletions.
There are no files selected for viewing
This file contains 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
20 changes: 20 additions & 0 deletions
20
docs/content/en/contributing/parser-documentation-template.md
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
--- | ||
title: "Parser Documentation Template" | ||
toc_hide: true | ||
weight: 1 | ||
--- | ||
|
||
Use this template as part of writing a new parser. | ||
|
||
* Copy this .md file and add it to docs/integrations/parsers/file in the GitHub repository | ||
* Update the title to match the name of your new parser | ||
* Fill out all sections listed below | ||
|
||
### File Types | ||
Specify all file types accepted by your parser. Include a process for creating the acceptable file from the related security tool. | ||
|
||
### Sample Scan Data / Unit Tests | ||
Add a link to the relevant unit tests or sample scan data folder in the GitHub repository. | ||
|
||
### Link To Tool | ||
A link to the scanner itself - (e.g. GitHub or appropriate vendor link) |
This file contains 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