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

Triggering a manual scan from user interface #224

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

Triggering a manual scan from user interface #224

v1r7u opened this issue May 5, 2020 · 0 comments
Labels
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/X

Comments

@v1r7u
Copy link
Contributor

v1r7u commented May 5, 2020

Users should be able to request new scans from Frontend application.

To accomplish the goal, scanner apps should run in queue-listening mode. Then scan scheduling could be triggered from Backend service instead of separate k8s cron-jobs only as it is now.

I think this task could work as an enhancement on top of scanners-refactoring #91 and page with scan results #208

As an idea, the user interface could be similar to ci tools, when you can see previous runs and can schedule new ones.

Opened questions:

  • User interface design
  • How to support both options in the same product: queue-triggered scans and independent cron-jobs
@v1r7u v1r7u added kind/enhancement New feature or request lifecycle/backlog General backlog pile. Any idea, which could be taken into work size/X labels May 5, 2020
@v1r7u v1r7u changed the title Trigering a manual scan from user interface Triggering a manual scan from user interface May 5, 2020
@v1r7u v1r7u added the priority/medium Medium priority issues label May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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/X
Projects
None yet
Development

No branches or pull requests

1 participant