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

fix: added extra args in trivy cmds #5146

Merged
merged 4 commits into from
May 22, 2024
Merged

fix: added extra args in trivy cmds #5146

merged 4 commits into from
May 22, 2024

Conversation

ashishdevtron
Copy link
Contributor

@ashishdevtron ashishdevtron commented May 21, 2024

Description

Fixes #5047

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?


@ashishdevtron ashishdevtron changed the title fix: added extra args fix: added extra args in trivy cmds May 21, 2024
Copy link

gitguardian bot commented May 22, 2024

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
10190659 Triggered Generic High Entropy Secret 2e2d68d wireNilChecker.env View secret
10190660 Triggered Generic Password 2e2d68d tests/integrationTesting/devtron-secret.yaml View secret
10190661 Triggered Generic Password 2e2d68d wireNilChecker.env View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Copy link

sonarcloud bot commented May 22, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@ashishdevtron ashishdevtron merged commit 282c0ff into main May 22, 2024
7 of 8 checks passed
@ashishdevtron ashishdevtron deleted the query-fix branch May 22, 2024 14:26
@kartik-579 kartik-579 restored the query-fix branch May 24, 2024 08:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature: Option to add CA.crt in image-scanner
2 participants