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

Implement additional Katalogus filter options #191

Open
jpbruinsslot opened this issue Jan 2, 2023 · 1 comment
Open

Implement additional Katalogus filter options #191

jpbruinsslot opened this issue Jan 2, 2023 · 1 comment
Labels
boefjes Issues related to boefjes

Comments

@jpbruinsslot
Copy link
Contributor

From: #201


At the moment the scheduler tries to keep track of organizations the consumed type of boefje and normalizers in cached internal data representations. This is used by the scheduler to match an OOI type with potentially available boefjes.

  • This implementation can result in more overhead when we scale to many organizations.
  • The cache invalidation of those cached internal data representations could potentially lead to unforeseen data race conditions.
  • Now there is a wait time for plugins and/or organizations that are enabled/created and not yet present in the internal data representation

Extend the katalogus plugin endpoint to filter on the consumed type of a plugin, organization id, and plugin type.

@zcrt
Copy link
Contributor

zcrt commented Feb 1, 2023

Additionally, it would be nice filter the katalogus based on input/output objects. (E.g. show me all boefjes that will produce a Certificate object.)

@dekkers dekkers added the boefjes Issues related to boefjes label Feb 15, 2023
@dekkers dekkers transferred this issue from minvws/nl-kat-boefjes Feb 15, 2023
ammar92 pushed a commit that referenced this issue Feb 24, 2023
@jpbruinsslot jpbruinsslot mentioned this issue May 9, 2023
36 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
boefjes Issues related to boefjes
Projects
None yet
Development

No branches or pull requests

3 participants