simar7

> Sounds good. For example, will the policy bundle renamed to the check bundle? Sounds reasonable. After all it is a bundle of checks 😄

Just an update on this: Most of the work is done to be able to do this restructuring, the last step being renaming the `trivy-policies` repo to `trivy-checks`. We'll do...

> @simar7 The documentation, cli flags and code still use the term `policy`. Will this be updated? That's right. Once we have the `trivy-polcies` repo renamed to `trivy-checks`, we can...

> a couple of questions: > > 1. If this removing an existing advertised feature? should we mark it as break or feat? Yes we're planning to drop scanning of...

Discuss here https://github.com/aquasecurity/trivy/discussions/5950

> > This is a breaking change. > > It is described above In #5950, so should we change the title prefix from "feat(misconf)" to "BREAKING CHANGE(miscong)"? e.g. #1571 thanks,...

Update Feb 2024: We've found a better approach to keep and improve the terraform plan scanning functionality. As it turns out, we can unzip the plan contents (it is a...

@nikpivkin could you add the action items needed to be performed to close this issue in the description?

> Personally, I would like to add namespace, but I am concerned that I am introducing unnecessary complexity. > > Of course, if there are more than 1,000 plugins, namespace...

Another idea we can have is a CLI option to ignore deprecated checks such as: `--ignore-deprecated-checks`