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

Print both vulnerabilities and violations tables if needed #163

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

attiasas
Copy link
Contributor

@attiasas attiasas commented Sep 1, 2024

  • The pull request is targeting the dev branch.
  • The code has been validated to compile successfully by running go vet ./....
  • The code has been formatted properly using go fmt ./....
  • All static analysis checks passed.
  • All tests have passed. If this feature is not already covered by the tests, new tests have been added.
  • All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

If --vuln flag was provided in table format. we only printed the vulnerabilities and not both

@attiasas attiasas added the bug Something isn't working label Sep 1, 2024
@attiasas attiasas added the safe to test Approve running integration tests on a pull request label Sep 1, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Sep 1, 2024
Copy link

github-actions bot commented Sep 2, 2024

👍 Frogbot scanned this pull request and did not find any new security issues.


@@ -160,6 +161,10 @@ func (auditCmd *AuditCommand) CommandName() string {
return "generic_audit"
}

func (auditCmd *AuditCommand) HasViolationContext() bool {
return len(auditCmd.watches) > 0 || auditCmd.projectKey != "" || auditCmd.targetRepoPath != ""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why targetRepoPath is here?

Copy link
Contributor Author

@attiasas attiasas Sep 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you provide repoPath they can infer the project as far as I know and violations returns

--repo-path                      [Optional] Target repo path, to enable Xray to determine watches accordingly.

@attiasas attiasas merged commit aea8b7c into jfrog:dev Sep 4, 2024
11 checks passed
@attiasas attiasas deleted the set_imagetag_as_target_name branch September 4, 2024 10:56
@lweitzel01
Copy link

After upgrading the jf cli from 2.63.2 to 2.67.0, it is no longer printing the Security Violations and License Compliance Violations table in the console output.

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

Successfully merging this pull request may close these issues.

3 participants