Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Story] As a system adminthat wants to script a protection, I do so without maintaining a fork of Draupnir #21

Open
Gnuxie opened this issue Jun 28, 2024 · 0 comments

Comments

@Gnuxie
Copy link
Member

Gnuxie commented Jun 28, 2024

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.

Issues

Total Pain

8

@Gnuxie Gnuxie changed the title [Story] As a system admin or developer who wants to script a protection, I do so without maintaining a fork of Draupnir [Story] As a system adminthat wants to script a protection, I do so without maintaining a fork of Draupnir Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant