Add JSON Schema for .trivyignore.yaml configuration file

[stdedos]

Description

Similarly to #9970, add schema for https://trivy.dev/docs/latest/configuration/filtering/#trivyignoreyaml

Target

None

Scanner

None

[knqyf263]

This seems like a reasonable request, and providing a JSON Schema would be a nice quality-of-life improvement for users editing .trivyignore.yaml in IDEs.

Before we prioritize the implementation, we'd like to get a sense of how broadly this is needed. If you're interested in this feature, please give a 👍 reaction on the original post so we can gauge community demand.

[stdedos]

I mean ... it is not "that crazy" to write that page as a JSONSchema format 😕

And you already have it for trivy.yaml

"True, you are inheriting the maintenance burden" - but ... it is not "crazy implementation burden"

[knqyf263]

The point here isn't implementation effort. In OSS, writing the initial schema is often the easy part — the real cost is long-term maintenance. Once we ship and document it as an official schema, users depend on it, and keeping it in sync with every future change to .trivyignore.yaml becomes an ongoing obligation. Removing or breaking it later is not straightforward, even when it turns out few people actually use it.

That's why we ask for reactions before prioritizing: not because the schema is hard to write, but because every accepted feature becomes a permanent commitment. Taking on that commitment for something only a handful of users benefit from isn't a decision we make lightly.

Of course, nothing stops anyone from generating and publishing a JSON Schema for .trivyignore.yaml independently — that's a great way to validate real-world demand before we take it on officially. We're not saying no; we'd just like to see that demand before committing to carry it indefinitely.