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.

Sign up for GitHub

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

Jump to bottom

SecHub Client: Produce Warning when --add-scm-history is 'true' for non compatible scan types #3392

Open
hamidonos opened this issue Aug 27, 2024 · 0 comments
Open

SecHub Client: Produce Warning when --add-scm-history is 'true' for non compatible scan types #3392

hamidonos opened this issue Aug 27, 2024 · 0 comments
Assignees
@sven-dmlr
Labels
client
Milestone
Client 1.8.0

Comments

@hamidonos
Copy link
Collaborator

Situation

Currently the client will always upload the scm folders when the --add-scm-history flag is set even if the scan type is not secret scan.

Solution

  • Log a warning when the flag is set to true for non-secret scan types
@hamidonos hamidonos added this to the Client 1.7.0 milestone Aug 27, 2024
@sven-dmlr sven-dmlr modified the milestones: Client 1.7.0, Client 1.8.0 Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sven-dmlr sven-dmlr

Labels
client
Projects
None yet
Milestone
Client 1.8.0
Development

No branches or pull requests
2 participants
@sven-dmlr @hamidonos