Currently in order to develop a protection, the user of draupnir has to essentially maintain a fork, keeping their protections in src/protections. This not only complicates maintenance but also makes it very inconvenient to develop protections and share them with others. So we figure the solution is to allow protections to be standalone.
Acceptance Criteria
There is a complete working example for an external protection that can be cloned and will just work. This will be used by the system admin as a template to script with.
There is a complete working example of a capability provider and capability renderer.
The protection provides working custom commands to be used as an example by the system admin.
External protections are loaded before Draupnir starts.
The directories to load external protections from can be configured in Draupnir's config file.
Currently in order to develop a protection, the user of draupnir has to essentially maintain a fork, keeping their protections in
src/protections. This not only complicates maintenance but also makes it very inconvenient to develop protections and share them with others. So we figure the solution is to allow protections to be standalone.Acceptance Criteria
Issues
Total Pain
8