Closed danielnbalasoiu closed 2 years ago
Hi! Can you pls give me an estimation when I can test a possible fix? Thanks!
Hi! Please let me know if you need me to test this. I'll happily provide debug information.
Hi @rammatzkvosky
Do you have any updates?
Thank you!
ping
@rammatzkvosky
@NatalyaDalid, can you please help me with a status on this matter? Thank you!
Hi @danielnbalasoiu , sorry for the late reply. We started working on this feature which will also cover this issue.
At the moment I still don't have an estimation when we would be able to deliver it , but the work is in progress and we will do our best to provide it in advance.
Hi @rammatzkvosky
This is great news! Please keep me in the loop and let me know if you need any alpha implementation feedback.
Hi! Any progress on this issue?
Hi @danielnbalasoiu,
The pre-release version with the fix will be available by the end of this week. We will keep you updated.
Thanks, WS PS Team
Hi @danielnbalasoiu ,
Please check the pre-release version : https://pypi.org/project/ws-nexus-integration/0.3a1/
In this version :
NexusDockerReposImagesIncludes
parameter is for docker type repositories. - Comma-separated regex list of images expressions to be included.
For example,
NexusDockerReposImagesIncludes=.*3.12
will only pull and scan the images which end in 3.12
Hi,
I have tested version 0.3a1
with NexusDockerReposImagesIncludes
parameter and it works as expected! 🥳 👏
In combination with ThreadCount
parameter the scan time improves drastically.
Hi @danielnbalasoiu ,
That's great! Thanks for letting us know.
I will keep this issue open until we will provide an official release.
Is your feature request related to a problem? Please describe.
It's almost impossible to scan large Nexus repositories without a huge amount of disk space and bandwidth. Context: There is a Nexus container registry which stores > 10k images. In the current implementation, a list with all containers is created, then the containers are downloaded and scanned. The problems are:
Describe the solution you'd like
A possible option would be implementing scanning in batches and then delete/clean up (see FR #38 the scanned containers.
The official UA supports scanning container images hosted in AWS ECR and supports configurable parameters:
Additional context
![image](https://user-images.githubusercontent.com/46020698/157035253-937a71f8-d51a-468a-a3fd-5302869b25fb.png)