refactor(scanner): propagate context to scanners/analyzers

[zsoltkacsandi]

Description

Passing context to scanners/analyzers.

Type of Change

[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[X] Refactor
[ ] Documentation
[ ] Other (please describe)

Checklist

• I have read the contributing guidelines
• Existing issues have been referenced (where applicable)
• I have verified this change is not present in other open pull requests
• Functionality is documented
• All code style checks pass
• New code contribution is covered by automated tests
• All new and existing tests pass

[paralta]

LGTM 🚀

[ramizpolic]

LGTM! 🚀

[ramizpolic]

Note: CIS Docker Benchmark scanner needs to be updated upstream to support contexts being passed when used as a library. It should either be added as part of Config or directly in calling function at https://github.com/Portshift/dockle/blob/4f3b165086b7adbaf853ece809c7c61497bb52d7/pkg/run.go#L44. Without this, we cannot force exit for CIS Docker scanner. This can be done in another PR once there is support for passing ctx in Dockle.

[akijakya]

Note: CIS Docker Benchmark scanner needs to be updated upstream to support contexts being passed when used as a library. It should either be added as part of Config or directly in calling function at https://github.com/Portshift/dockle/blob/4f3b165086b7adbaf853ece809c7c61497bb52d7/pkg/run.go#L44. Without this, we cannot force exit for CIS Docker scanner. This can be done in another PR once there is support for passing ctx in Dockle.

Wouldn't that be a breaking change for the Dockle scanner? Time for our own fork? 😃 A ticket should be created for this anyway if there isn't one already...

[ramizpolic]

Note: CIS Docker Benchmark scanner needs to be updated upstream to support contexts being passed when used as a library. It should either be added as part of Config or directly in calling function at https://github.com/Portshift/dockle/blob/4f3b165086b7adbaf853ece809c7c61497bb52d7/pkg/run.go#L44. Without this, we cannot force exit for CIS Docker scanner. This can be done in another PR once there is support for passing ctx in Dockle.

Wouldn't that be a breaking change for the Dockle scanner? Time for our own fork? 😃 A ticket should be created for this anyway if there isn't one already...

It wont be a breaking change for Dockle. @zsoltkacsandi has a way to address this in a backwards compatible way by making the run function that performs the scan in Dockle public.

[github-actions]

Hey!

Your images are ready:

• ghcr.io/openclarity/vmclarity-apiserver-dev:pr1741-474da7ba703b469c1e23d902dc8b24819806804a
• ghcr.io/openclarity/vmclarity-cli-dev:pr1741-474da7ba703b469c1e23d902dc8b24819806804a
• ghcr.io/openclarity/vmclarity-cr-discovery-server-dev:pr1741-474da7ba703b469c1e23d902dc8b24819806804a
• ghcr.io/openclarity/vmclarity-orchestrator-dev:pr1741-474da7ba703b469c1e23d902dc8b24819806804a
• ghcr.io/openclarity/vmclarity-plugin-kics-dev:pr1741-474da7ba703b469c1e23d902dc8b24819806804a
• ghcr.io/openclarity/vmclarity-ui-dev:pr1741-474da7ba703b469c1e23d902dc8b24819806804a
• ghcr.io/openclarity/vmclarity-ui-backend-dev:pr1741-474da7ba703b469c1e23d902dc8b24819806804a