doc: introduce verifier type #43
Conversation
junczhu
requested review from
akashsinghal,
binbin-li,
luisdlp,
susanshi and
toddysm
as code owners
✅ Deploy Preview for ratify-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
docs/reference/verifier.md
Outdated
|
|
||
| | Property | Type | IsRequired | Description | | ||
| | -------- | -------- | -------- | --------- | | ||
| | name | string | true |The name of the plugin that should match with plugin binary on disk. Must not contain characters disallowed in file paths for the system (e.g. / or \) | | ||
| | name | string | true |The name of the plugin that should match with plugin binary on disk. Must not contain characters disallowed in file paths for the system (e.g. / or \). `name` can be customized when `type` has been specified. | |
There was a problem hiding this comment.
Maybe we should mention that when type is not provided, name would behave like type.
There was a problem hiding this comment.
The binary naming is also confusing to me. If only the name is specified then the binary name must match but otherwsie the binary must match the type field right?
|
@junczhu do you think we should update all the configs and verifier report samples we have in the docs to add the |
We can discuss that at the next community meeting. As discussed, I would open a new PR for the updates, and comment about the change applies to the release version 1.1.0 and this change is backward compatible. |
introduce verifier type to the
verifier specandverification result version