Package Directory Structure

Content code entities in Demisto are presented by YAML files.

Automation scripts and integrations YAML files include Javascript/Python code.

Python scripts and integrations are stored in directories as packages.

This is required for running linting and unit testing on the Python code.

The package is converted into a YAML file, which include all the package components, in Demisto's CI build, using the script, and then populated in the Content release.

├── <INTEGRATION-NAME>.py // Integration / automation script Python code.
├── <INTEGRATION-NAME> // Python unit test code.
├── <INTEGRATION-NAME>.yml // Configuration YAML file.
├── <INTEGRATION-NAME>_image.png // Integration PNG logo (for integrations only).
├── <INTEGRATION-NAME> // Detailed instructions markdown file (for integrations only)
├── // Markdown file which include the script/integration release notes.
├── // Integration / automation script documentation.
├── Pipfile // Can be copied from Tests/scripts/dev_envs/default_python3
└── Pipfile.lock // Can be copied from Tests/scripts/dev_envs/default_python3
  • Integration logo conventions:
    • Size up to 4KB.
    • Dimensions of 120x50.
    • Transparent background.
    • Dark version of the logo.
  • Note: Since Python 2.7 will not be maintained past 2020, we refer only to Python 3 for the Pipfile.

For example, a package of the integration Palo Alto Networks Cortex is stored under Integrations directory in a sub-directory named PaloAltoNetworksCortex and contain the following files:

└─── .PaloAltoNetworksCortex
│ ├──
│ ├──
│ ├── PaloAltoNetworksCortex.yml
│ ├── PaloAltoNetworksCortex_image.png
│ ├──
│ ├──
│ ├── Pipfile
| └── Pipfile.lock

You can extract a package from a YAML file by using the following:

  • Demisto IntelliJ Plugin
  • script from the Content repository.
    • Usage example: python3 -i /Integrations/integration-WildFire.yml -o Integrations/WildFire -m

Integration logo standard

Integration Logo Standard

Last updated on