Adding integration tests for trivy security scanner #650
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Upon merging, this PR will add integration tests for the trivy security scanner.
This will close #623.
Contrary to what has been discussed there, downloading the database for trivy during the integration tests does not seem to be an issue. The tests took only about 35s.
Successful download of the database has also been stated in the trivy logs.
If the tests prove to be unstable, however, it could be considered to add an offline version of the trivy database as described here. This would pose the need for a scanner dockerfile created by us instead of the official image, where a version of the database would be included. Integration tests could be run with the "--skip-update" flag afterwards.
Checklist
npm testruns for the whole project.