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

Display linters' command in logs #4205

Open
VictorRos opened this issue Oct 30, 2024 · 1 comment
Open

Display linters' command in logs #4205

VictorRos opened this issue Oct 30, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@VictorRos
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Not directly.

Describe the solution you'd like

In MegaLinter logs, for each linter I would like to have the linter command run by MegaLinter

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

With recent trivy problems, we are trying to set up a workaround for our repositories that use MegaLinter prior to 8.1.0.

I tried to set trivy environment variables (TRIVY_*) or adding trivy command options to download the database vulnerability but it still try to download it from GHCR registry instead of AWS registry I set up.

So I would like to see the command MegaLinter is using when calling trivy.

It could be useful to see all linters commands in logs so we know what options are set by our configuration or the default MegaLinter configuration.

What are your though about that?
Is there already a way to display them?

@VictorRos VictorRos added the enhancement New feature or request label Oct 30, 2024
@echoix
Copy link
Collaborator

echoix commented Oct 30, 2024

Set the env var LOG_LEVEL to DEBUG. It should to it https://megalinter.io/latest/config-variables/

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

No branches or pull requests

2 participants