Documentation is a critical step that assists customers who may use your integration by providing insight into how the integration is supposed to work. From creating custom playbooks, to providing background information to assist in debugging, it is important to ensure that the documentation explains every aspect of the integration.
Note: The documentation must conform to the Integration Doc Format.
Within Demisto, exists the ability to generate documentation for your integration. First verify that the DocumentationAutomation script exists in your content by navigating to the Automation tab in Demisto.
First, take the YAML file of your integration and upload it to the War Room. Please note the entry ID as you will need it in the next step.
To use the DocumentationAutomation script, navigate to the War Room and execute the command:
You may choose to include the other arguments depending on what you may need.
Once the command has been executed, you will see the documentation html in the War Room as a new entry and a copy of it as a file entry. Review the generated document.
Where there is missing information, be sure to fill out the document completely. It is advised to include use-cases, screenshots, and examples of the context.
Documentation must be generated if:
- If the integration is new then you are required to create new documentation.
- If the integration is existing but missing documentation then please create new documentation.
- If the integration is existing and some of the integration has changed. For example, a new command was added, context was changed, or anything else; please update the documentation.
Using commands parameter
To automatically generate example output (human readable and context), you should create a text file containing command examples, one per line. The command examples should appear the same way they would as in the CLI in Demisto, for example
Commands will be executed one at a time, in the order in which they appear in the file. If there are duplicates of a command included in the text file, only the output of the command's first execution will be included in the generated documentation output.
Example for commands file:
!ip ip=22.214.171.124!domain domain=demisto.com
- Microsoft Graph Groups: Shows how the commands and examples should be presented.
- Slack v2: Shows an example of the troubleshooting section.
The documentation should be posted in the integration/automation script package directory as a