archive
/
PurpleDome
mirror of https://github.com/avast/PurpleDome
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
develop
polishing2
presentation_gpn_2022
more_unit_tests
extending_page
main
caldera_4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5e91d09b79'
${ noResults }
PurpleDome/plugins
History
Thorsten Sick b2fc4c81d4 Extended documentation 3 years ago
..
base Extended documentation 3 years ago
default some git cleanup 3 years ago
README.md Added plugins 4 years ago

README.md

Plugin reasoning and planning. To be deleted later.

Which parts to make into plugins

  • Everything that could be contributed by external people
  • Very specialized features

At the moment those are:

  • kali attacks
  • sensors
  • vm_controllers
  • post_processors

Parts of a plugin

  • Plugin specific configuration
  • The plugin python code
  • Additional files and tools to be used by the plugin

Therefore: We need a specific folder for every plugin

We want out own plugins plus external plugins to throw in. So we will have a default folder for plugins (ours) and additional folders with names chosen by external people. Plugins must be searched in those folders.

Picking and loading plugins

  • the experiment.yaml config specifies the plugins to use

Found plugin interfaces

https://github.com/ironfroggy/straight.plugin https://github.com/tibonihoo/yapsy ( -: not maintained anymore, sourceforge) https://github.com/pytest-dev/pluggy/ ( -: not maintained anymore; +: used by tox and similar)