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.

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

In JF CLI v 2.71.3, scanning with --repo-path does not generate violations #233

Open
Morielp-jfrog opened this issue Nov 13, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Morielp-jfrog
Copy link

Describe the bug

In JF CLI v 2.71.3, scanning (jf s \ jf docker scan) with --repo-path is not generating violations.

Current behavior

Scanning (jf s \ jf docker scan) with --repo-path is not generating violations.
--watches flag is working as expected and generating violations.

Reproduction steps

Scan a binary using jf s \ scan a docker image using jf docker scan, with the --repo-path flag.

Expected behavior

Getting violations according to the watches that are configured for the mentioned repository.

JFrog CLI-Security version

2.71.3

JFrog CLI version (if applicable)

2.71.3

Operating system type and version

NA

JFrog Xray version

3.106.7

@Morielp-jfrog Morielp-jfrog added the bug Something isn't working label Nov 13, 2024
@Morielp-jfrog Morielp-jfrog changed the title In JF CLI v 2.71.3, --repo-path is not generating violations In JF CLI v 2.71.3, scanning with --repo-path does not generate violations Nov 13, 2024
@attiasas
Copy link
Contributor

Thank you for reporting this.
The issue will be fixed here: #241

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants