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

[Feature] Add endpoint to return a list of available plugins. #1689

Closed
YourTechBud opened this issue Jun 17, 2023 · 0 comments
Closed

[Feature] Add endpoint to return a list of available plugins. #1689

YourTechBud opened this issue Jun 17, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request p/high Candidate for being included in the upcoming release
Milestone

Comments

@YourTechBud
Copy link
Collaborator

The problem faced currently?

There is no way to figure out how many plugins are available/ registered in SC.

How can we solve it?

  • Each Source which feeds into a plugin (eg. OPAPolicySource) should implement a source.Plugin interface.
  • The interface will be defined by the source manager.
  • The Plugin interface will have just one method, GetPluginDetails() which returns a struct containing name, driver and schema.
    • Name will be the name of the source
    • Driver will be the handler which needs to be initialised for that plugin (for OPAPolicySource, the driver will be opa).
    • Params will always be nil for now.
  • The Source manager should expose an api /sc/v1/plugins which returns array of plugins registered.

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you.
👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request p/high Candidate for being included in the upcoming release
Projects
Status: Done
Development

No branches or pull requests

2 participants