-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Trivy Executing Incorrect Plugin. #1086
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
This issue is stale because it has been labeled with inactivity. |
github-actions
bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and will be auto-closed.
label
Aug 24, 2021
knqyf263
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and will be auto-closed.
label
Sep 1, 2021
@afdesk Could you look into it? |
afdesk
added a commit
to afdesk/trivy
that referenced
this issue
Sep 2, 2021
There is a closure inside a function for Action field: variable p always refers on the last plugin. solution: redefine variable inside the for loop. Fixes aquasecurity#1086
knqyf263
pushed a commit
that referenced
this issue
Sep 2, 2021
There is a closure inside a function for Action field: variable p always refers on the last plugin. solution: redefine variable inside the for loop. Fixes #1086
liamg
pushed a commit
that referenced
this issue
Jun 7, 2022
There is a closure inside a function for Action field: variable p always refers on the last plugin. solution: redefine variable inside the for loop. Fixes #1086
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Trivy is executing the wrong plugin. I have two plugins installed. My own and the kubectl example one. When I try to execute my own plugin it executes the kubectl plugin.
Output of run with
-debug
:Output of
trivy -v
:Work around
Uninstalling the kubectl plugin with
trivy plugin uninstall kubectl
will allow my trivy to run my own plugin.The text was updated successfully, but these errors were encountered: