VerifierReport should contain both verifierType and verifierName while using Rego Policy

[binbin-li]

What happened in your environment?

Currently Verifier interface exposes a Name() API for querying the name of the verifier.

However, this only works well for 1 verifier of each type. If we want to support multiple verifiers of the same type, it would be difficult for users to distinguish between verification results from those verifiers.
Take the notation verifier as an example:

The metadata.name is the actual name for each verifier, and spec.name is the verifierType. The current implementation of Name() API returns the spec.name which could not help distinguish between verifiers of the same type.

And in the CLI mode, the verifier config even doesn't include the spec.name as it's not in the spec.

What did you expect to happen?

In both CLI and k8s add-on mode, Ratify should return a verifierReports that contains both verifierName and verifierType which could be used to be evaluated by Rego policy.

What version of Kubernetes are you running?

No response

What version of Ratify are you running?

No response

Anything else you would like to add?

No response

Are you willing to submit PRs to contribute to this bug fix?

• Yes, I am willing to implement it.