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.

Sign up for GitHub

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

Jump to bottom

Vulnerability data should enter into database at import time #1198

Closed
TG1999 opened this issue May 17, 2023 · 2 comments
Closed

Vulnerability data should enter into database at import time #1198

TG1999 opened this issue May 17, 2023 · 2 comments
Assignees
@TG1999
Labels
Data collection import-improver-migration
Milestone
v33.0.0

Comments

@TG1999
Copy link
Contributor

TG1999 commented May 17, 2023

Currently, when we run any importer, only the advisory table is populated and we have to run the default improver to enter the imported advisory data into other tables, instead, we should enter all the imported advisories at that from a particular importer at the time of import itself.
@TG1999 TG1999 self-assigned this May 17, 2023
@TG1999 TG1999 added this to the v33.0.0 milestone May 17, 2023
@Hritik14
Copy link
Collaborator

Isn't handling of version constraints a job for improver and importer is supposed to only scrape data as it is from the internet?

@TG1999
Copy link
Contributor Author

TG1999 commented Sep 22, 2023

Completed in #1280

@TG1999 TG1999 closed this as completed Sep 22, 2023
@TG1999 TG1999 mentioned this issue Sep 22, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TG1999 TG1999

Labels
Data collection import-improver-migration
Projects
None yet
Milestone
v33.0.0
Development

No branches or pull requests
2 participants
@Hritik14 @TG1999