Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

Refactor multiple scanner projects into a single dotnet solution #91

Open
v1r7u opened this issue Mar 5, 2020 · 0 comments
Open

Refactor multiple scanner projects into a single dotnet solution #91

v1r7u opened this issue Mar 5, 2020 · 0 comments
Assignees
@v1r7u
Labels
area/scanner Issue relates to Scanners services kind/enhancement New feature or request lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/medium Medium priority issues size/M

Comments

@v1r7u
Copy link
Contributor

v1r7u commented Mar 5, 2020

Refactor multiple scanners into a single solution, which can run given external application (polaris, azsk, trivy, kube-bench, ...)
This refactoring opens more options to reuse code and can simplify:

  • adding new scanner types
  • running each scanner in different modes
    • one-time job, listening to the queue (for example, might be useful to support triggered from UI scans)
    • scheduled job
@v1r7u v1r7u added the area/scanner Issue relates to Scanners services label Mar 5, 2020
@v1r7u v1r7u added this to the v1 milestone Mar 5, 2020
@v1r7u v1r7u self-assigned this Mar 5, 2020
@v1r7u v1r7u modified the milestones: v1-internal, v1-public Mar 23, 2020
@v1r7u v1r7u added the lifecycle/backlog General backlog pile. Any idea, which could be taken into work label May 5, 2020
@v1r7u v1r7u removed this from the v2 milestone May 5, 2020
@v1r7u v1r7u mentioned this issue May 5, 2020
Open
@v1r7u v1r7u added kind/enhancement New feature or request size/M priority/medium Medium priority issues labels May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@v1r7u v1r7u

Labels
area/scanner Issue relates to Scanners services kind/enhancement New feature or request lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/medium Medium priority issues size/M
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@v1r7u