Skip to content
This repository has been archived by the owner on May 1, 2023. It is now read-only.

Zap lambda: Migrate to reading grouped requests (URL's) via Job id #73

Closed
mohdnr opened this issue Aug 13, 2021 · 4 comments
Closed

Zap lambda: Migrate to reading grouped requests (URL's) via Job id #73

mohdnr opened this issue Aug 13, 2021 · 4 comments

Comments

@mohdnr
Copy link
Contributor

mohdnr commented Aug 13, 2021

JOB_Id which is the same for all of the URLs from a given request. So we can tie all of the things that are run from a given request together.

@maxneuvians
Copy link
Contributor

I am trying to figure out if job_id should be scan_id or a template_id from #9 instead

@dj2
Copy link
Contributor

dj2 commented Aug 24, 2021

I'm going to add some comments to #9 as it needs to be updated slightly I think.

@dj2
Copy link
Contributor

dj2 commented Aug 24, 2021

Actually, nm, I think job_id would be scan_id ...

@mohdnr
Copy link
Contributor Author

mohdnr commented Dec 14, 2021

scan_id & report_id's are being used to group results.

@mohdnr mohdnr closed this as completed Dec 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants