DivvyCloud

Welcome to the DivvyCloud Docs!

DivvyCloud is a Cloud Security Posture Management (CSPM) platform that provides real-time analysis and automated remediation across leading cloud and container technologies.

For questions about documentation reach out to us [email protected]

Take Me to the Docs!    Release Notes

Overview

Plugins are Python packages that are loaded when a DivvyCloud process starts. These are primarily used for registering custom filters and packaging frontend assets to extend the user interface.

Since Plugins are largely a developer feature if you are looking more in-depth or advanced information, refer to our developer repository.

Loading and Unloading

To install, simply copy the plugin directory to the plugins folder and it will be automatically be loaded into the software when the process starts.

dev-box$ cp -r plugin_instance_type_blacklist plugins/
dev-box$ ls -alh plugins/
total 48
drwxr-xr-x   9 cderamus  staff   306B Sep 12 07:57 .
drwxr-xr-x  74 cderamus  staff   2.5K Sep 12 07:27 ..
-rw-r--r--   1 cderamus  staff   2.0K Sep 12 07:57 plugin_instance_type_blacklist

For docker-compose deployments, the location of the plugins folder on your local filesystem is defined by mounting it as ./plugins inside the container. In our recommended docker-compose.yaml, this folder is named plugins and in the same directory as docker-compose.yaml, as defined by the volumes: directive here:

volumes:
      - ./plugins:/plugins

To remove a plugin from the system you can either remove the file from the plugins folder or simply delete the directory permanently. The snippet below illustrates the removal of the example plugin from the example section.

dev-box$ rm -rf plugins/plugin_instance_type_blacklist
dev-box$ ls -alh plugins/
total 48
drwxr-xr-x   9 cderamus  staff   306B Sep 12 07:57 .
drwxr-xr-x  74 cderamus  staff   2.5K Sep 12 07:27 ..

Updates

Simply copy/rsync your updates into the plugin directory and restart all processes.

Updated 7 months ago

Plugins


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.