An API for ssh_scan (https://github.com/mozilla/ssh_scan) and the backend API service for the Mozilla SSH Observatory (https://observatory.mozilla.org/)
31
stars
8
forks
source link
In progress scan polling returns weak/confusing messaging #25
1.) I use the API to task a scan
2.) I then poll the API periodically to see when the scan is completed
3.) During that window of waiting for the scan, we provide very little feedback to the end user about what's happening (currently just { scan: "not found" } until the scan comes back)
This is particially due to the currently implemented crude queuing strategy in place where it's not maintaining state or bound to the DB in any way. Once this is DB integrated we should provide active status for the end user so they can bubble that feedback back to the user.
Scenario:
1.) I use the API to task a scan 2.) I then poll the API periodically to see when the scan is completed 3.) During that window of waiting for the scan, we provide very little feedback to the end user about what's happening (currently just { scan: "not found" } until the scan comes back)
This is particially due to the currently implemented crude queuing strategy in place where it's not maintaining state or bound to the DB in any way. Once this is DB integrated we should provide active status for the end user so they can bubble that feedback back to the user.