How to point to the tricky.yaml when it is not in the root of the workspace

Question

How to point to the tricky.yaml when it is not in the root of the workspace

Opened this issue a year ago · 2 comments

How do you point to the configuration file when it is not in the root directory of the workspace? We are using megalinter as a CI gates, and would like to use the configuration file for the project that is located in a subdirectories instead of the route of the workspace. That way the vs code scan use the same configuration as CI gates.

Answer 1 · 2023-07-30T11:41:04.000Z

Can the extension support fixed trivy CLI arguments? like --config ./.github/linters/trivy.yaml

Answer 2 · 2023-08-03T15:54:27.000Z

Would you be open to us pushing a PR to allow extension setting to point to a tryivy.yaml config file? Also, if that is done should we ignore the other extension setting if they are set in the config file.