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

feat: add govulncheck for checking whether ArgoCD has CVE #21928

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sivchari
Copy link
Contributor

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

I added govulncheck workflow to check whether ArgoCD has CVE.

@sivchari sivchari requested review from a team as code owners February 21, 2025 02:18
Copy link

bunnyshell bot commented Feb 21, 2025

✅ Preview Environment deployed on Bunnyshell

Component Endpoints
argocd https://argocd-stdiyi.bunnyenv.com/
argocd-ttyd https://argocd-web-cli-stdiyi.bunnyenv.com/

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔴 /bns:stop to stop the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

@sivchari sivchari changed the title add govulncheck for checking whether ArgoCD has CVE feat: add govulncheck for checking whether ArgoCD has CVE Feb 21, 2025
@sivchari
Copy link
Contributor Author

Copy link

codecov bot commented Feb 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.83%. Comparing base (7870200) to head (fbe37a8).

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #21928   +/-   ##
=======================================
  Coverage   53.83%   53.83%           
=======================================
  Files         341      341           
  Lines       57004    57004           
=======================================
  Hits        30689    30689           
+ Misses      23720    23718    -2     
- Partials     2595     2597    +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant